Mantis - gdb
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5251 regular use major always 2015-09-03 19:39 2015-09-03 19:39
Reporter: brianvandenberg Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
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 */
Steps To Reproduce:
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 .
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2015-09-03 19:39 brianvandenberg New Issue

There are no notes attached to this issue.