On 15-04-04 03:45 PM, lmx wrote:
Hi guys,
I am running geany without problems for some years from now...
today i experienced a weird thing...
I decided to run vangrind against my code...
well...now i can't use gdb :(
I can compile and run the process, but not debug it...
when I try to open a file with fopen or use calloc, or malloc, the geany debuger trows me some erros :(
like this for malloc/calloc:
"Can't find a source file "/home/aurel32/eglibc/eglibc-2.17/malloc/malloc.c""
"home/aurel"??? why? wtf..
Another errors: when I try to access a FILE * pointer, for a regular file, that exists!
Can't find a source file "/home/aurel32/eglibc/eglibc-2.17/libio/iofgets.c"
I can't work...but I can compile??don't understand this...
for what I understand valgrind is controlling the binary file, and this process, is afther that "corrupted" right ??
but even then, deleting it, compiling again with gcc...running it ok, debuguing it...i can't.
some info from valgrind report fther running my code against it:
==9423== Invalid write of size 4 ==9423== at 0x4E87037: _IO_vfscanf (vfscanf.c:1857) ==9423== by 0x4E8EBC4: __isoc99_vsscanf (isoc99_vsscanf.c:43) ==9423== by 0x4E8EB46: __isoc99_sscanf (isoc99_sscanf.c:32) ==9423== by 0x40143B: file_to_holder (ihx.c:267) ==9423== by 0x400E59: ihx_read (ihx.c:130) ==9423== by 0x40159B: main (main.c:16) ==9423== Address 0x51df44d is 13 bytes inside a block of size 16 alloc'd ==9423== at 0x4C2B514: calloc (vg_replace_malloc.c:593) ==9423== by 0x4013E1: file_to_holder (ihx.c:261) ==9423== by 0x400E59: ihx_read (ihx.c:130) ==9423== by 0x40159B: main (main.c:16) ==9423==
why is geany looking for "/home/aurel32/eglibc/eglibc-2.17/malloc/malloc.c"" when a malloc intruction occurrs in the code???
does any one have any idea how to solve this?
Hi,
Geany doesn't have a debugger or Valgrind support, so I guess you are using one of the debugging plugins? I would try to clean build and get it running outside of Geany from the command line, after your build issues are sorted out (ex. it looks like you're linking "eglibc" in your home directory rather than some system-wide C stdlib, maybe on purpose?), I bet it will work with any of the debugging plugins. Valgrind should be totally unrelated to any of this.
Cheers, Matthew Brush