|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| get stack trace from C program on Solaris 8 | rydahl | Filesystems, Disks and Memory | 4 | 03-23-2007 10:53 AM |
| help required - stack trace | ranj@chn | UNIX for Advanced & Expert Users | 9 | 09-26-2006 05:20 AM |
| Need to capture ERROR msg and stack trace | gswhoops | Shell Programming and Scripting | 2 | 01-11-2006 04:51 PM |
| BackTrace | wojtyla | High Level Programming | 6 | 10-04-2005 06:38 AM |
| Core file without a readable stack trace | ciregbu | High Level Programming | 0 | 10-02-2002 08:42 AM |
 |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
11-02-2005
|
|||
|
|||
|
printing a stack trace with backtrace
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form? I am using Red Hat and the program is written in c++. 
|
| Forum Sponsor | ||
|
|
|
#3
11-03-2005
|
|||
|
|||
|
Really has nothing to do with redhat, or backtrace (whatever that is). C++ just mangles names, so you have to live with it. Those are the names of your functions and that is as human readable as it's getting. I believe the managling is just encoding the parms into the name of the function/method so as to support polymorphism.
|
|||
| Google The UNIX and Linux Forums |
Linear Mode
