From: Paul Litvak <paullitvak@gmail.com>
To: gdb-patches@sources.redhat.com
Subject: View backtraces for core dumps generated under OS X 10.4.8 on intel macs
Date: Thu, 02 Nov 2006 19:19:00 -0000 [thread overview]
Message-ID: <03FD4AE3-7C29-4C01-A2EB-5C48292E5FE2@gmail.com> (raw)
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:
--- src/gdb/macosx/core-macho.c 2005-08-04 15:41:17.000000000 -0500
+++ /Users/plitvak/src/darwin/gdb/src/gdb/macosx/core-macho.c
2006-10-19 04:57:49.000000000 -0500
@@ -77,7 +77,7 @@ check_thread (bfd *abfd, asection *asect
#if defined (TARGET_POWERPC)
const char *expected = "LC_THREAD.PPC_THREAD_STATE.";
#elif defined (TARGET_I386)
- const char *expected = "LC_THREAD.i386_THREAD_STATE.";
+ const char *expected = "LC_THREAD.x86_THREAD_STATE.";
#else
#error "unsupported architecture"
#endif
@@ -280,7 +280,7 @@ core_fetch_section_registers (asection *
#if defined (TARGET_POWERPC)
ppc_macosx_fetch_gp_registers ((gdb_ppc_thread_state_t *) regs);
#elif defined (TARGET_I386)
- i386_macosx_fetch_gp_registers ((gdb_i386_thread_state_t *) regs);
+ i386_macosx_fetch_gp_registers ( (gdb_i386_thread_state_t*)&
((gdb_x86_thread_state_t *) regs)->uts.ts32 );
#else
#error "unsupported architecture"
#endif
-- Paul Litvak
next reply other threads:[~2006-11-02 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 19:19 Paul Litvak [this message]
2006-11-02 19:21 ` Daniel Jacobowitz
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=03FD4AE3-7C29-4C01-A2EB-5C48292E5FE2@gmail.com \
--to=paullitvak@gmail.com \
--cc=gdb-patches@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