Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Stan Shebs <stan@codesourcery.com>,
	 Michael Snyder <msnyder@vmware.com>,
	 n179911 <n179911@gmail.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How to configure gdb to support '--arch=i386' on Mac OS X
Date: Thu, 08 Oct 2009 07:53:00 -0000	[thread overview]
Message-ID: <D3895F25-4F7E-479D-910A-45AC5BF3B862@adacore.com> (raw)
In-Reply-To: <20091007231809.GA21992@bromo.med.uc.edu>


On Oct 8, 2009, at 1:18 AM, Jack Howarth wrote:

> On Wed, Oct 07, 2009 at 02:22:20PM -0700, Stan Shebs wrote:
>> Michael Snyder wrote:
>>> Yeahhhh, this isn't going to work.
>>>
>>> Your binary is in... I forget what it's called -- oh, "mach-o"  
>>> format.
>>> Our (fsf) gdb does not know how to read that file format.  And it
>>> would be a huge job to port over the changes in apple gdb that tell
>>> it how to read mach-o files (besides the fact that they are "fat"
>>> files, or at least potentially might be). m
>> The Mach-O part does work in 7.0, thanks to Tristan and AdaCore  
>> (check
>> out gdb/machoread.c).  I don't think fatness-handling is there,  
>> although
>> at the Xcode level one has to specifically ask for fat builds  
>> anyway, so
>> one could avoid that particular obstacle and thus be well- 
>> positioned to
>> smack one's face into the next wall. :-)
>>
>> Stan
>>
>
> Stan,
>  I am puzzled about the fact that the current x86_64-apple-darwin10
> build of FSF gdb 7.0 is unable to load i386 binaries like x86_64 gdb
> can under linux. Do you think this should be possible without  
> resorting
> to fat-binaries for darwin?

That's unexpected.  It least it worked in the past.  Will try to fix  
that.

Tristan.


  reply	other threads:[~2009-10-08  7:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 18:09 n179911
2009-10-07 18:32 ` Joel Brobecker
2009-10-07 18:35 ` Michael Snyder
2009-10-07 20:10   ` n179911
2009-10-07 20:20     ` Daniel Jacobowitz
2009-10-07 20:21       ` n179911
2009-10-07 21:16         ` Stan Shebs
2009-10-07 20:26     ` n179911
2009-10-07 20:38       ` Matt Rice
2009-10-07 21:07       ` Michael Snyder
2009-10-07 21:22         ` Stan Shebs
2009-10-07 23:18           ` Jack Howarth
2009-10-08  7:53             ` Tristan Gingold [this message]
2009-10-08 12:48             ` Tristan Gingold
2009-10-08  7:54           ` Tristan Gingold
2009-10-07 21:04     ` Michael Snyder
2009-10-07 21:15       ` Jack Howarth
2009-10-07 20:45 ` Jack Howarth

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=D3895F25-4F7E-479D-910A-45AC5BF3B862@adacore.com \
    --to=gingold@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=howarth@bromo.med.uc.edu \
    --cc=msnyder@vmware.com \
    --cc=n179911@gmail.com \
    --cc=stan@codesourcery.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