Backtrace extraction ONLY gdb

Maucci, Cyrille
Fri Apr 22 20:49:00 GMT 2011

Hi All,

I've just found

This looks like what I need.


-----Original Message-----
From: Maucci, Cyrille 
Sent: Sunday, March 27, 2011 10:25 PM
To: 'Jan Kratochvil'
Cc: Joel Brobecker; Eli Zaretskii;
Subject: RE: Backtrace extraction ONLY gdb

Hey Jan,

Thanks for the pointers.
The ABRT project is very interesting.

Concerning the presence of a host on the LAN where multi-GB xfers are not an issue, it is very rarely the case.


-----Original Message-----
From: Jan Kratochvil []
Sent: Thursday, March 24, 2011 6:25 AM
To: Maucci, Cyrille
Cc: Joel Brobecker; Eli Zaretskii;
Subject: Re: Backtrace extraction ONLY gdb

On Wed, 23 Mar 2011 23:51:42 +0100, Maucci, Cyrille wrote:
> 	. the core files are multi GB large and the 'separate' host is not located on the customer network.
> 	. you not only need the core files but the libs to debug the core.
> 	Indeed, you could argue to setup a 'replica' system to read the core
> 	file, but when you've got dozens of customers with dozens of different
> 	software versions, this becomes the nightmare.

This is solved by the ABRT project
automatically getting the right binaries and debug info versions by the build-id present in any binary and core file (with properly configured GCC).

It is now deploying a .
If there are security concerns about running GDB locally (as ABRT has been doing before RetraceServer so far) isn't there located a host for backtraces in LAN where multi-GB transfers are not an issue?


More information about the Gdb mailing list