From: Daniel Jacobowitz <drow@false.org>
To: Paul Litvak <paullitvak@gmail.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: View backtraces for core dumps generated under OS X 10.4.8 on intel macs
Date: Thu, 02 Nov 2006 19:21:00 -0000 [thread overview]
Message-ID: <20061102192129.GA800@nevyn.them.org> (raw)
In-Reply-To: <03FD4AE3-7C29-4C01-A2EB-5C48292E5FE2@gmail.com>
On Thu, Nov 02, 2006 at 01:18:12PM -0600, Paul Litvak wrote:
> The bug:
>
> Can't view backtraces for core dumps generated under OS X 10.4.8 on
> intel macs.
> GDB reports "Core file contained no thread-specific data" after
> loading the core file.
> I can reproduce the bug with gdb in Xcode 2.4 and 2.4.1
>
> The patch to Apple's gdb-563 sources:
Apple's GDB sources bear fairly little relationship to the FSF GDB
sources, which are all that we on this list can change; I recommend you
report this directly to Apple.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-02 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 19:19 Paul Litvak
2006-11-02 19:21 ` Daniel Jacobowitz [this message]
2006-11-02 19:32 ` Jim Ingham
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=20061102192129.GA800@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=paullitvak@gmail.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