gnu gdb malloc return inaccessible pointer [closed]

问题

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.

Closed 6 years ago.

malloc in gdb debug session returns inaccessible address after running some codes.

first break at the start of main function. everything is ok.

Breakpoint 9, main (argc=5, argv=0x7fffffffe418) at src/ose/sdv/ose_sdv/linux/main.c:557
557     char *cfgfile = NULL;
(gdb) call malloc(4)
$50 = 23293968
(gdb) x 23293968
0x1637010:  0x00000000
(gdb) c

after running some lines it begins to return inaccessible memory address which is start at 0xffffffff~

Program received signal SIGINT, Interrupt.0x00007ffff70c1f4d in read () from /lib64/libc.so.6
(gdb) call malloc(4)
$52 = -1811110576
(gdb) x -1811110576
0xffffffff940ca550: Cannot access memory at address 0xffffffff940ca550

i'm using a 64bit linux os.

i cannot find the exact line of code that causes this.

The line after which malloc begins to like this is always change.

No exception occurred during runtime and the program runs as expected. I am not sure what is wrong here.

回答1:

There are bugs in your program. Bugs in C++ don't always give exceptions, and C has no notion of exceptions. Read about undefined behavior.

When typing call malloc(4) under gdb you ask gdb to call malloc inside your buggy process.

The reason why malloc (or new) may give different addresses from one run to the next is ASLR. You could disable ASLR if you wanted to by

 echo 0 > /proc/sys/kernel/randomize_va_space

You should compile with gcc -Wall -g and use gdb as a debugger (perhaps the watch command of gdb could be useful).

What might have happened is that you wrongly overwrote some word outside a heap malloc-ed memory zone, or got a buffer overflow, or used an uninitialized variable, etc...

^{A good way to mess malloc really badly is to write before some malloc-ed zone like int *p = malloc(4); p[-1]=1234; then future free and malloc could exhibit very weird behavior...}

And you should use valgrind to hunt your memory bugs. Try running

valgrind yourprogram your-program-arguments ....

With a recent GCC (i.e 4.8) you could also try compiling and linking with -fsanitize=address option (in addition to -Wall -g)

来源：https://stackoverflow.com/questions/16747073/gnu-gdb-malloc-return-inaccessible-pointer