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: Mon, 09 Jan 2006 19:12:00 -0000	[thread overview]
Message-ID: <200601091912.k09JC0fp022663@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <43C22DD0.5080503@netspace.net.au> (message from Russell Shaw on 	Mon, 09 Jan 2006 20:33:04 +1100)

> Date: Mon, 09 Jan 2006 20:33:04 +1100
> From: Russell Shaw <rjshaw@netspace.net.au>
> 
> Hi,
> When i make my code core-dump using abort(), and read the
> core with "target core core", the back-trace shows a corrupted
> stack. How do i make a core dump that has an intact stack i can
> trace thru? Should i use something other than abort()?

Sorry, but you don't provide nearly enough information to enable us to
answer your question.  At least we need to know what OS, what hardware
platform, what version of GDB and what version of GCC you're using.
It'd help us even more if you could provide a typescript of a GDB
session that show us your problem.

Thanks,

Mark


  reply	other threads:[~2006-01-09 19:12 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 [this message]
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
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=200601091912.k09JC0fp022663@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