Home » Language IDEs » C / C++ IDE (CDT) » Problems w/ Debug Configs, Attach to Application(Standard Attach to Process Launcher is not working.)
| Problems w/ Debug Configs, Attach to Application [message #871244] |
Fri, 11 May 2012 15:36 |
 Rich Podraza
Messages: 1
Registered: May 2012 |
Junior Member |
|
|
My original problem is that debug symbols (debug-time data about class variables, etc.) is unreliable and I was getting the error mi_cmd_var_update: Usage: NAME." From previous web searches I found that most people found GDB (DSF) Attach to Process Launcher unreliable, and that I should use Standard Attach to Process Launcher.
However, Standard Attach to Process Launcher doesn't even get started. The first thing I see is it breaks in __kernel_vsyscall() but shows in red "No source available for "__kernel_vsyscall()". Then the console shows the following output:
.gdbinit: No such file or directory.
Using host libthread_db library "/lib64/libthread_db.so.1".
75-gdb-set confirm off
75^done
(gdb)
76-gdb-set width 0
76^done
(gdb)
77-gdb-set height 0
77^done
(gdb)
78-interpreter-exec console echo
78^done
(gdb)
79-gdb-show prompt
79^done,value="(gdb) "
(gdb)
80-gdb-set auto-solib-add on
80^done
(gdb)
81-gdb-set stop-on-solib-events 0
81^done
(gdb)
82-gdb-set stop-on-solib-events 1
82^done
(gdb)
83 attach 32083
&"attach 32083\n"
&"warning: Lowest section in shared object read from target memory is .hash at ffffe0b4\n"
attach 32083
warning: Lowest section in shared object read from target memory is .hash at ffffe0b4
~"`shared object read from target memory' has disappeared; keeping its symbols.\n"
`shared object read from target memory' has disappeared; keeping its symbols.
83^done,thread-id="0",frame={addr="0xffffe410",func="__kernel_vsyscall",args=[]}
(gdb)
84-environment-directory /eau/home/rpodraza/workspace/AXIv2Master /eau/home/rpodraza/workspace/AXIv2Master/.settings
84^done,source-path="/eau/home/rpodraza/workspace/AXIv2Master:/eau/home/rpodraza/workspace/AXIv2Master/.settings:$cdir:$cwd"
(gdb)
85 info threads
&"info threads\n"
85^done
(gdb)
86-data-list-register-names
86^done,register-names=["eax","ecx","edx","ebx","esp","ebp","esi","edi","eip","eflags","cs","ss","ds","es","fs","gs","st0","st1","st2","st3","st4","st5","st6","st7","fctrl","fstat","ftag","fiseg","fioff","foseg","fooff","fop","xmm0","xmm1","xmm2","xmm3","xmm4","xmm5","xmm6","xmm7","mxcsr","orig_eax","mm0","mm1","mm2","mm3","mm4","mm5","mm6","mm7"]
(gdb)
87-stack-info-depth
87^done,depth="5"
(gdb)
88-stack-list-frames 0 5
88^done,stack=[frame={level="0",addr="0xffffe410",func="__kernel_vsyscall"},frame={level="1",addr="0x003e9001",func="??"},frame={level="2",addr="0xf7f23028",func="??"},frame={level="3",addr="0x00000005",func="??"},frame={level="4",addr="0x00000000",func="??"}]
(gdb)
89-break-insert AXIv2_Master.cpp:129
89^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x00025f26",func="AXI_Master::update()",file="AXIv2_Master.cpp",line="129",times="0"}
(gdb)
90-stack-list-arguments 0 0 0
90^done,stack-args=[frame={level="0",args=[]}]
(gdb)
91-stack-list-locals 0
91^done,locals=[]
(gdb)
I am using Eclipse 3.7.2, gdb 6.3, g++ 4.2.2. Any ideas?
|
|
|
Goto Forum:
Current Time: Thu Apr 25 20:03:33 GMT 2024
Powered by FUDForum. Page generated in 0.02585 seconds |
] 
Search
Help
Register
Login
Home
