From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: backtrace issues
Date: Fri, 06 Feb 2004 19:20:00 -0000 [thread overview]
Message-ID: <yf2r7x8f23k.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <yf2wu70f49k.fsf@hawaii.kealia.com> (David Carlton's message of "Fri, 06 Feb 2004 10:32:07 -0800")
On Fri, 06 Feb 2004 10:32:07 -0800, David Carlton <carlton@kealia.com> said:
> Does GDB have known issues with backtraces on programs compiled with a
> recent GCC but with a C library compiled with an old GCC?
Actually, the fact that the program was compiled with a recent GCC
seems to be irrelevant.
I did come up with a stripped-down test case; I've filed PR gdb/1545
about it.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2004-02-06 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 18:32 David Carlton
2004-02-06 19:20 ` David Carlton [this message]
2004-02-07 4:25 ` Joel Brobecker
2004-02-10 22:22 ` Andrew Cagney
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=yf2r7x8f23k.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--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