Anonymous | Login | 2024-04-23 11:12 CEST |
Main | My View | View Issues |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
0005251 | [gdb] regular use | major | always | 2015-09-03 19:39 | 2015-09-03 19:39 | |||||||
Reporter | brianvandenberg | View Status | public | |||||||||
Assigned To | ||||||||||||
Priority | normal | Resolution | open | |||||||||
Status | new | |||||||||||
Summary | 0005251: Symbol info not loaded when attaching to a running process | |||||||||||
Description |
I believe the following bug post describes the exact same issue: https://sourceware.org/bugzilla/show_bug.cgi?id=17903 [^] This works: ~ gdb my_executable --pid=1234 /* ... */ (gdb) where /* stack trace gets listed correctly */ This does not: ~ gdb (gdb) attach 1234 /* ... */ (gdb) where /* stack trace with lots of addresses and question marks */ |
|||||||||||
Additional Information |
Assuming this and the other bug I linked to refer to the same issue, their belief is the mechanism gdb is using to discover the executable based on the pid isn't compatible with Solaris. This is causing difficulties in gui debuggers because they tend to just attach using a pid without giving the executable path. There is a work around: ~ gdb (gdb) attach 1234 /* ... */ (gdb) file /path/to/file (gdb) sharedlibrary . |
|||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
|
There are no notes attached to this issue. |
Copyright © 2000 - 2008 Mantis Group |