RE: [GD-Linux] signals and exceptions

[Michael R. <mi...@sw...>]

I suspect what is needed may be found in GNU binutils, but you'll have to do
some hunting.

See demangle.h for cplus_demangle, anyhow.

regards,

~m

> -----Original Message-----
> From: gam...@li...
> [mailto:gam...@li...]On Behalf Of Mads
> Bondo Dydensborg
> Sent: Saturday, November 17, 2001 2:55 AM
> To: D. Stimits
> Cc: gam...@li...
> Subject: Re: [GD-Linux] signals and exceptions
>
>
> On Fri, 16 Nov 2001, D. Stimits wrote:
>
> > Now maybe someone could answer this; I added -rdynamic and it improved
> > the output by naming functions, but the arguments to the function were
> > still not useful, they still look like offsets rather than what my
> > sample had (like calling a function with an int of 1, then 2, then 3, so
> > on...and showing up as something far different). Is there some way to
> > expand on this debugging to get even more information, such as local
> > variable values and formatted (meaningful) argument call values?
>
> I am sorry I do not know the answer to your question. gdb can do this, so
> I suppose there is a way to do it, although I do not know if there are any
> built in functions you can use.
>
> I did write a simple perl script to demangle c++ names and get file:line
> information, which follows here: