Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: rjshaw@netspace.net.au
Cc: gdb@sources.redhat.com
Subject: Re: Core dumps
Date: Tue, 10 Jan 2006 19:16:00 -0000	[thread overview]
Message-ID: <200601101916.k0AJGOgg009366@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <43C39AAB.6000505@netspace.net.au> (message from Russell Shaw on 	Tue, 10 Jan 2006 22:29:47 +1100)

> 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?

> In gdb, i did:
> 
> (gdb) target core core
> (gdb) bt
> 
> I get a long backtrace of "?" and a note saying corrupt stack.
> 
> I can't get a new core file to happen now, despite the
> program hitting abort() or raise(11). I have ulimit unlimited.

Well, I can't be of much help then.

Mark



  reply	other threads:[~2006-01-10 19:16 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 [this message]
2006-01-10 21:41       ` Daniel Jacobowitz
2006-01-11  1:21         ` Russell Shaw
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=200601101916.k0AJGOgg009366@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb@sources.redhat.com \
    --cc=rjshaw@netspace.net.au \
    /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