Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Maucci, Cyrille" <cyrille.maucci@hp.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	Eli Zaretskii <eliz@gnu.org>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Backtrace extraction ONLY gdb
Date: Sun, 27 Mar 2011 20:26:00 -0000	[thread overview]
Message-ID: <0E02F16954AF394BB163AEE50FDF5485690156E0AF@GVW1121EXC.americas.hpqcorp.net> (raw)
In-Reply-To: <20110324052431.GA24500@host1.jankratochvil.net>

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.

++Cyrille

-----Original Message-----
From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com] 
Sent: Thursday, March 24, 2011 6:25 AM
To: Maucci, Cyrille
Cc: Joel Brobecker; Eli Zaretskii; gdb@sourceware.org
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 https://fedorahosted.org/abrt/wiki
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 http://fedoraproject.org/wiki/Features/RetraceServer .
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?


Regards,
Jan


  reply	other threads:[~2011-03-27 20:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 17:13 Maucci, Cyrille
2011-03-21 18:49 ` Eli Zaretskii
2011-03-23 22:17   ` Maucci, Cyrille
2011-03-23 22:43     ` Joel Brobecker
2011-03-23 22:51       ` Maucci, Cyrille
2011-03-24  5:25         ` Jan Kratochvil
2011-03-27 20:26           ` Maucci, Cyrille [this message]
2011-04-22 20:49           ` Maucci, Cyrille
2011-04-22 20:54             ` Jan Kratochvil
2011-03-24 10:25         ` Pedro Alves
2011-03-24 11:09           ` Maucci, Cyrille
2011-03-24 10:28       ` Steffen Dettmer
2011-03-24 13:01         ` Jan Kratochvil
2011-03-22 16:46 ` Tom Tromey
2011-03-23 22:21   ` Maucci, Cyrille
2011-03-24 17:13     ` Tom Tromey
2011-03-24 17:20     ` Jan Kratochvil
2011-03-24 19:00       ` Maucci, Cyrille

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0E02F16954AF394BB163AEE50FDF5485690156E0AF@GVW1121EXC.americas.hpqcorp.net \
    --to=cyrille.maucci@hp.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox