public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Olivier Crete <tester@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] fix binary debug support, part elevenity billion
Date: Tue, 17 Jan 2006 13:01:29 -0500	[thread overview]
Message-ID: <1137520889.28568.9.camel@cocagne.max-t.internal> (raw)
In-Reply-To: <200601171803.48108@enterprise.flameeyes.is-a-geek.org>

On Tue, 2006-17-01 at 18:03 +0100, Diego 'Flameeyes' Pettenò wrote:
> On Tuesday 17 January 2006 17:51, Olivier Crete wrote:
> > The argument in favor of splitdebug is that it allows users to give
> > useful bugreports when using tools such as gnome's bug-buddy.
> Erm actually it does not. Unless gnome herd fixed it recently.
> The same goes for KCrashHandler/Dr Konqui.

It does on my system, bug-buddy just spawned GDB (and it has worked that
way for as long as I can remember). So you just need gdb 5/6 and it
should work without problems with splitdebug.


-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-01-17 18:06 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15  6:11 [gentoo-dev] fix binary debug support, part elevenity billion Mike Frysinger
2006-01-15  6:19 ` Joshua Baergen
2006-01-15  7:19   ` Mike Frysinger
2006-01-15 11:52 ` Henrik Brix Andersen
2006-01-15 12:12   ` Mike Frysinger
2006-01-15 15:33 ` Olivier Crête
2006-01-17 15:11   ` Richard Fish
2006-01-17 16:12     ` Mike Frysinger
2006-01-17 16:51     ` Olivier Crete
2006-01-17 17:03       ` Diego 'Flameeyes' Pettenò
2006-01-17 18:01         ` Olivier Crete [this message]
2006-01-19  3:03           ` [gentoo-dev] " R Hill
2006-01-15 18:25 ` [gentoo-dev] " Dan Meltzer
2006-01-15 22:28   ` Mike Frysinger
2006-01-19 22:56 ` [gentoo-dev] fix binary debug support, part elevenity billion 1/2 Mike Frysinger
2006-01-19 23:17   ` Olivier Crete
2006-01-19 23:26     ` Henrik Brix Andersen
2006-01-20  0:15     ` Danny van Dyk
2006-01-20  0:32     ` Mike Frysinger
2006-01-19 23:25   ` Henrik Brix Andersen
2006-01-19 23:33   ` solar
2006-01-19 23:52     ` Mark Loeser
2006-01-20  0:28       ` Mike Frysinger
2006-01-20  8:09         ` Kevin F. Quinn (Gentoo)
2006-01-20  0:30     ` Mike Frysinger
2006-01-20  7:52     ` Kevin F. Quinn (Gentoo)
2006-01-20  3:24   ` Donnie Berkholz
2006-01-20  3:40     ` Ciaran McCreesh
2006-01-20  6:25   ` Harald van Dijk
2006-01-20 12:10     ` Mike Frysinger
2006-01-20 13:53       ` Harald van Dijk
2006-01-20 23:25       ` Robin H. Johnson
2006-01-24 20:25         ` Paul de Vrieze
2006-01-22  4:12   ` Marius Mauch
2006-01-22 19:45     ` Mike Frysinger
2006-01-22 21:30       ` Marius Mauch
2006-01-22 20:50         ` Mike Frysinger
2006-01-23  1:12         ` Donnie Berkholz
2006-01-23 18:28           ` "Environement categories" (was Re: [gentoo-dev] fix binary debug support, part elevenity billion 1/2) Danny van Dyk
2006-01-23 19:44             ` Mike Frysinger
2006-01-24  6:44             ` Brian Harring
2006-01-25  1:06               ` Mike Frysinger
2006-01-25  7:26                 ` Brian Harring
2006-01-29 14:40                   ` Mike Frysinger
2006-01-24 22:56 ` [gentoo-dev] fix binary debug support, part elevenity billion Donnie Berkholz
2006-01-25  1:04   ` Mike Frysinger

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=1137520889.28568.9.camel@cocagne.max-t.internal \
    --to=tester@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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