Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Russell Shaw <rjshaw@netspace.net.au>
Cc: gdb@sources.redhat.com
Subject: Re: Core dumps
Date: Wed, 11 Jan 2006 01:21:00 -0000	[thread overview]
Message-ID: <43C45D89.9030408@netspace.net.au> (raw)
In-Reply-To: <20060110214131.GA1686@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Tue, Jan 10, 2006 at 08:16:24PM +0100, Mark Kettenis wrote:
> 
>>>Date: Tue, 10 Jan 2006 22:29:47 +1100
>>>From: Russell Shaw <rjshaw@netspace.net.au>
>>>
>>>I'm using debian-sid.
>>
>>Well, that narrows it down...
>>
>>...but not nearly enough.  Well, I suppose you're on i386 GNU/Linux.
>>
>>
>>>GNU gdb 6.3-debian
>>>gcc (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)
>>
>>So that's a Debian-modified gdb, have you tried asking for help on any
>>of the Debian lists?
> 
> It's only lightly modified (by me).  But, I would need the same
> information that Mark's been asking for in order to help...
> especially, actual traces of GDB output.

What's the best way to force a core-dump from my own code?
(I couldn't find much on the net)


  reply	other threads:[~2006-01-11  1:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09  9:33 Russell Shaw
2006-01-09 19:12 ` Mark Kettenis
2006-01-10 11:29   ` Russell Shaw
2006-01-10 19:16     ` Mark Kettenis
2006-01-10 21:41       ` Daniel Jacobowitz
2006-01-11  1:21         ` Russell Shaw [this message]
2006-01-11  1:43           ` Larry Martell
2006-01-11  1:52             ` Russell Shaw
2006-01-11  4:19               ` Eli Zaretskii
2006-01-11  4:41                 ` Russell Shaw
2006-01-11  4:45                   ` Joel Brobecker
2006-01-11  4:57                     ` Russell Shaw
2006-01-11 14:39                   ` Larry Martell
2006-01-10 11:30   ` Russell Shaw
2006-11-30  3:26 ` Bapi
2006-11-30  4:52   ` Nick Roberts

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=43C45D89.9030408@netspace.net.au \
    --to=rjshaw@netspace.net.au \
    --cc=gdb@sources.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