From: Michael Snyder <msnyder@vmware.com>
To: n179911 <n179911@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How to configure gdb to support '--arch=i386' on Mac OS X
Date: Wed, 07 Oct 2009 21:04:00 -0000 [thread overview]
Message-ID: <4ACD0176.6070008@vmware.com> (raw)
In-Reply-To: <3b9893450910071310s5225e440pb1b6eaa1d62f69db@mail.gmail.com>
n179911 wrote:
> Thank you. You are right.
>
> The gdb comes with apple has '-arch' option, but gdb 7.0 does not.
>
> $ /usr/bin/gdb --help
> --translate Debug applications running under translation.
> -arch i386|armv6|x86_64|ppc Specify a gdb targetting a specific
> architecture
>
> So should I do what Joel Brobecker suggested in adding that option in
> gdb/main.c?
Or you could try to make XCode refrain from sending it.
Entirely up to you. I don't think we are looking to add that
to the mainstream gdb.
> On Wed, Oct 7, 2009 at 11:31 AM, Michael Snyder <msnyder@vmware.com> wrote:
>> n179911 wrote:
>>> Hi,
>>>
>>> I have compiled gdb 7.0 on Mac OS X. And I have configured XCode to
>>> use this new version of gdb 7.0.
>>>
>>> But when I start debug my XCode project it said gdb can't recognize
>>> the option '--arch=i386'. Here is the log of my error:
>>>
>>> [Session started at 2009-10-07 11:00:43 -0700.]
>>> /Users/n179911/bin/gdb/bin/gdb: unrecognized option `--arch=i386'
>>> Use `/Users/n179911/bin/gdb/bin/gdb --help' for a complete list of
>>> options.
>>>
>>> The Debugger has exited with status 1.The Debugger has exited with status
>>>
>>> Can you please tell me how to build gdb to support '--arch-i386' option?
>> I don't think this has ever been a command line option in fsf gdb.
>> Maybe it is one that was added to Apple's version of gdb.
>>
>> Try running `/Users/n179911/bin/gdb/bin/gdb --help', and
>> then run the same command using your installed gdb that came
>> with Mac OS. My guess is that the Mac version will list
>> "--arch" among the command line options, but the fsf version
>> will not (mine doesn't).
>>
>>
next prev parent reply other threads:[~2009-10-07 21:04 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
2009-10-08 12:48 ` Tristan Gingold
2009-10-08 7:54 ` Tristan Gingold
2009-10-07 21:04 ` Michael Snyder [this message]
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=4ACD0176.6070008@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=n179911@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