Home » Language IDEs » C / C++ IDE (CDT) » Debugger problem
| | | |
Re: Debugger problem [message #704533 is a reply to message #704491] |
Thu, 28 July 2011 19:06 |
dd Messages: 4 Registered: July 2011 |
Junior Member |
|
|
well, I get the feeling I'm not setting up the program properly. The source compiles, build, debugs, and runs on our windows setup, but in Linux/Eclipse we can get it to compile/build, but are running into this snag getting the debugger going.
Also, it seems to indicate the program counter is either at address 0x0 or 0x1 when the "seg fault".
Edit:
heres a pic of what I mean
-
Attachment: debugger.png
(Size: 1.08MB, Downloaded 384 times)
[Updated on: Thu, 28 July 2011 21:05] Report message to a moderator
|
|
|
Re: Debugger problem [message #705175 is a reply to message #704533] |
Fri, 29 July 2011 14:36 |
dd Messages: 4 Registered: July 2011 |
Junior Member |
|
|
a little more info from the gdb trace console window:
602,028 ~"ESI:\e[0m"
602,028 ~" 0x00000000 \e[32m"
602,028 ~"EDI:\e[0m"
602,028 ~" 0x00000000 \e[32m"
602,028 ~"EBP:\e[0m"
602,029 ~" 0x00000000 \e[32m"
602,029 ~"ESP:\e[31m"
602,029 ~" 0xBFFFF394 \e[32m"
602,029 ~"EIP:\e[0m"
602,029 ~" 0x00000001\n "
602,029 ~"\e[32m"
602,029 ~"CS:\e[0m"
602,029 ~" 0073 \e[32m"
602,029 ~"DS:\e[0m"
602,029 ~" 007B \e[32m"
602,029 ~"ES:\e[0m"
602,029 ~" 007B \e[32m"
602,029 ~"FS:\e[0m"
602,029 ~" 0000 \e[32m"
602,029 ~"GS:\e[0m"
602,029 ~" 0000 \e[32m"
602,029 ~"SS:\e[0m"
602,029 ~" 007B\e[0m"
602,052 &"Error while running hook_stop:\n"
602,055 &"Cannot access memory at address 0x1\n"
602,056 *stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation fault",\
frame={addr="0x00000001",func="??",args=[]},thread-id="1",stopped-threads="all",core="0"
602,059 (gdb)
(then a little farther down)
602,908 (gdb)
602,911 16-thread-info 1
602,984 17-data-disassemble -s 1 -e 45 -- 1
602,984 17^error,msg="Cannot access memory at address 0x1"
602,984 (gdb)
603,050 18-data-disassemble -s 0 -e 32 -- 1
603,051 18^error,msg="Cannot access memory at address 0x0"
603,051 (gdb)
603,087 19-data-disassemble -s 2 -e 54 -- 1
603,087 19^error,msg="Cannot access memory at address 0x2"
603,087 (gdb)
|
|
|
Re: Debugger problem [message #705192 is a reply to message #705175] |
Fri, 29 July 2011 14:54 |
Marc Khouzam Messages: 357 Registered: July 2009 |
Senior Member |
|
|
602,056 *stopped,reason="signal-received",signal-name="SIGSEGV",signal-meaning="Segmentation fault",\
frame={addr="0x00000001",func="??",args=[]},thread-id="1",stopped-threads="all",core="0"
means your program crashed. I don't know why GDB cannot report addr or func. Maybe your target is not reporting them.
Marc
|
|
|
Goto Forum:
Current Time: Fri Sep 20 09:32:14 GMT 2024
Powered by FUDForum. Page generated in 0.07029 seconds
|