Howto get a stack trace from coredumps now that we have abrt?

[Neal Becker]

Now that abrt is intercepting core dumps, what do I do to get a stack trace for 
a binary that is NOT a fedora package?  Either my own code, or something like, 
shall we say, just for the sake of argument, google chrome?

I know how to turn off sending core dumps to abrt, but I don't want to always 
run that way, and I don't know how to trigger this core dump.

[Neal Becker]

Tom Horsley wrote:

>  On Sun, 03 Mar 2013 09:12:47 -0500
>  Neal Becker wrote:
>  
> > Now that abrt is intercepting core dumps, what do I do to get a stack trace
> > for
> > a binary that is NOT a fedora package?  Either my own code, or something
> > like, shall we say, just for the sake of argument, google chrome?
> > 
> > I know how to turn off sending core dumps to abrt, but I don't want to always
> > run that way, and I don't know how to trigger this core dump.
> > 
>  
>  An excellent question. I know I have to utterly disable the abrt stuff
>  if I want to run my core file debugger tests on fedora systems at work.
>  I haven't found anything less drastic. 
Not acceptable.  I want to be able to use abrt for fedora packages, but I also 
need to be able to retroactively analyze a core dump (i.e., something crashed 
but I don't know how to recreate it).

[Tom Horsley]

On Sun, 03 Mar 2013 09:12:47 -0500
Neal Becker wrote:

>  Now that abrt is intercepting core dumps, what do I do to get a stack
> trace for 
>  a binary that is NOT a fedora package?  Either my own code, or something like, 
>  shall we say, just for the sake of argument, google chrome?
>  
>  I know how to turn off sending core dumps to abrt, but I don't want to always 
>  run that way, and I don't know how to trigger this core dump.
>   
An excellent question. I know I have to utterly disable the abrt stuff
if I want to run my core file debugger tests on fedora systems at work.
I haven't found anything less drastic.