Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: 代尔欣 <daierxin@gmail.com>
To: gdb@sourceware.org
Subject: Re: No useful backtrace in core dump.
Date: Thu, 22 Apr 2010 09:02:00 -0000	[thread overview]
Message-ID: <s2t8f4584b51004220202uf9ebc310s2341b6520b94082e@mail.gmail.com> (raw)
In-Reply-To: <20100422084947.GA7781@radix50.net>

http://sources.redhat.com/ml/gdb/2008-08/msg00123.html
From above thread:
Indeed, changing abort() to invalid memory reference makes backtrace work.
foo (int a, int b)
{
int c=40;
abort(); <--- IIUC, change to invalid memory reference
return a+b;
}

I don't know whether can remove the __attribute__((noreturn)) or not
when compiling glibc. It seems the problem a little complicated....

2010/4/22 Baurzhan Ismagulov <ibr@radix50.net>:
> On Thu, Apr 22, 2010 at 04:35:41PM +0800, 代尔欣 wrote:
>>       How about I use lower optimize option with GCC? If this still
>> can't work, I will follow your suggestion...
>
> IIUC, the thread implies that rebuilding glibc without
> __attribute__((noreturn)) for abort() should solve the problem, but I
> haven't tried that.
>
> With kind regards,
> --
> Baurzhan Ismagulov
> http://www.kz-easy.com/
>


  reply	other threads:[~2010-04-22  9:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22  2:41 代尔欣
2010-04-22  6:01 ` Baurzhan Ismagulov
2010-04-22  7:09   ` 代尔欣
2010-04-22  8:18 ` Mark Kettenis
2010-04-22  8:35   ` 代尔欣
2010-04-22  8:50     ` Baurzhan Ismagulov
2010-04-22  9:02       ` 代尔欣 [this message]
2010-04-22  9:17         ` Baurzhan Ismagulov
2010-04-22  9:36           ` 代尔欣
2010-04-22  9:44             ` Baurzhan Ismagulov

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=s2t8f4584b51004220202uf9ebc310s2341b6520b94082e@mail.gmail.com \
    --to=daierxin@gmail.com \
    --cc=gdb@sourceware.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