This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I have discovered that if you try to continue wihout breakpoint it sends a messages:On host: This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... (gdb) target remote 172.25.193.23:1023 Remote debugging using 172.25.193.23:1023 0x00008110 in _start () (gdb) b main Breakpoint 1 at 0x8158: file hello.c, line 4. (gdb) c Continuing. Program received signal SIGILL, Illegal instruction. 0x00008114 in _start () (gdb) On target(CDB89712) # gdbserver 172.25.140.19:1023 /armdevelop/hello Process /armdevelop/hello created; pid = 196 Remote debugging from host 172.25.140.19 hello(135): undefined instruction: pc=00008114 Code: e91ba800 e3a0b000 (e7ffdefe) e1a0100d e0812100 Killing inferior #This is a known problem between GDB 5.3 and uclibc: uclibc doesn't leave the identifying marks that GDB uses to figure out that something is a "Linux" binary rather than a "generic ELF" binary. Try a CVS snapshot of GDB and I bet it'll work.
Thank you Daniel,
I got a CVS snapshot and I have a little different result now.
I tried to compile it the same way (arm-linux) and using armv4l-unknown-linux option but in both cases result was the same "Segmentation fault"
Below I attached a debug output from gdb and gdbserver.
May be I am doing something plainly wrong?
Another interesting detail I noticed - in previous version I had 0x00008110 in _start () in this version 0x40000d20 in ?? ().
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |