Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.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:16:00 -0000	[thread overview]
Message-ID: <4ACD0518.5070104@codesourcery.com> (raw)
In-Reply-To: <3b9893450910071321s2e58e036ye9000d8b1ee08333@mail.gmail.com>

n179911 wrote:
> From
>
> http://developer.apple.com/mac/library/documentation/DeveloperTools/Reference/XcodeUserDefaultRef/100-Xcode_User_Defaults/UserDefaultRef.html#//apple%5Fref/doc/uid/TP40005535-CH3-SW54
>
> it mentions I can switch a different GDB in xcode.
>   
In practice, that is mostly useful for using different versions/releases 
of Apple's GDB, or for cross development.  The --arch issue is just the 
tip of the iceberg of problems you are likely to experience with trying 
to use FSF GDB.  The command set is different, output from commands is 
different, and Xcode has lots of assumptions about what the debugger can 
do, especially for the native case.

Stan


  reply	other threads:[~2009-10-07 21:16 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 [this message]
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
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=4ACD0518.5070104@codesourcery.com \
    --to=stan@codesourcery.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