From: Tristan Gingold <gingold@adacore.com>
To: Robert Lupton the Good <rhl@astro.princeton.edu>
Cc: gdb@sourceware.org
Subject: Re: Debugging 32/64 bit binaries on os/x 10.7 with cvs gdb?
Date: Wed, 30 Nov 2011 07:47:00 -0000 [thread overview]
Message-ID: <34BC371E-FD6A-4FD0-BF69-9746DB2F42A1@adacore.com> (raw)
In-Reply-To: <DCB78A22-26C6-4513-97B6-26EAE2A656DE@astro.princeton.edu>
On Nov 29, 2011, at 9:32 PM, Robert Lupton the Good wrote:
> If I build gdb from source on os/x 10.7 and attempt to debug python (a 32/64 bit binary), gdb says;
>
>> $ ~/Src/gnu/gdb/gdb /usr/bin/python
>> GNU gdb (GDB) 7.3.50.20111109-cvs
>> Copyright (C) 2011 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
>> and "show warranty" for details.
>> This GDB was configured as "x86_64-apple-darwin11.2.0".
>> For bug reporting instructions, please see:
>> <http://www.gnu.org/software/gdb/bugs/>...
>> "/usr/bin/python": not in executable format: File format not recognized
>> (gdb) quit
>> $ file !$
>> file /usr/bin/python
>> /usr/bin/python: Mach-O universal binary with 2 architectures
>> /usr/bin/python (for architecture x86_64): Mach-O 64-bit executable x86_64
>> /usr/bin/python (for architecture i386): Mach-O executable i386
>
> Is there a way to build gdb to work around this?
No. Currently gdb is not able to debug fat binary. Use lipo to extract the architecture you want to use.
prev parent reply other threads:[~2011-11-30 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 20:33 Robert Lupton the Good
2011-11-30 7:47 ` Tristan Gingold [this message]
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=34BC371E-FD6A-4FD0-BF69-9746DB2F42A1@adacore.com \
--to=gingold@adacore.com \
--cc=gdb@sourceware.org \
--cc=rhl@astro.princeton.edu \
/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