From: Jim Ingham <jingham@apple.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Gordon Prieur <Gordon.Prieur@Sun.COM>, gdb@sourceware.org
Subject: Re: Questions about gdb/mi support on the Mac
Date: Fri, 24 Aug 2007 18:30:00 -0000 [thread overview]
Message-ID: <77356E57-639F-4F6B-B39E-4395D6FC8B87@apple.com> (raw)
In-Reply-To: <20070824180208.GA18829@caradoc.them.org>
As Daniel said, we've pretty freely changed the MI interfaces to make
them work with ProjectBuilder, then "Project Builder" then Xcode.
When we started working on this 6 years ago, the MI interfaces were
pretty rudimentary, so this was necessary. And there wasn't much
interest in taking MI changes for the first couple of years we were
working on it here, so we gradually drifted apart.
There have been several rounds of pulling from our sources to the FSF
version by various kind folks on the net - though these often
introduced other subtler differences. I haven't ever catalogued what
we've changed, however, so I can't off the top of my head tell you
what is different. Most of the changes we made to input syntax are
documented either in our version of the manual, or in the function
headers to the mi implementation functions. The output changes are
less well documented. And in our sources we've tried to mark our
local diffs with "APPLE LOCAL"; but with the MI stuff, where there are
many whole sections of code that we've added, we are less careful
about this.
There was a short-lived attempt to rationalize the MI interfaces. It
seems to have gone quiet, however - I don't think anybody who's
actually working on gdb had sufficient motivation to make it worth the
time it would take to actually do this.
Jim
On Aug 24, 2007, at 11:02 AM, Daniel Jacobowitz wrote:
> On Fri, Aug 24, 2007 at 10:50:41AM -0700, Gordon Prieur wrote:
>> Hi,
>>
>> What are the known differences between running gdb/mi on a Mac and
>> on Windows/Linux/Solaris? I'm debugging problems in netbeans C/C++
>> support (via gdb) on the Mac and am seeing significant differences
>> between
>> the Mac and other platforms.
>
> If you are using GDB an Mac OS X, it is Apple's highly customized
> version to work with Xcode. You'd really have to ask them about it -
> it's got common ancestry with other versions of GDB, but has changed
> quite a lot to work better with their IDE.
>
> --
> Daniel Jacobowitz
> CodeSourcery
next prev parent reply other threads:[~2007-08-24 18:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 17:51 Gordon Prieur
2007-08-24 18:02 ` Daniel Jacobowitz
2007-08-24 18:30 ` Jim Ingham [this message]
2007-08-24 18:43 ` Bob Rossi
2007-08-25 9:56 ` Eli Zaretskii
2007-08-25 10:19 ` Bob Rossi
2007-08-28 8:49 ` André Pönitz
2007-08-28 8:29 ` André Pönitz
2007-08-28 8:56 ` Nick Roberts
2007-08-28 10:55 ` Daniel Jacobowitz
2007-08-28 11:24 ` Bob Rossi
2007-08-28 11:33 ` Daniel Jacobowitz
2007-08-28 12:53 ` Bob Rossi
2007-08-28 13:13 ` Daniel Jacobowitz
2007-08-28 13:37 ` Bob Rossi
2007-08-28 13:45 ` Daniel Jacobowitz
2007-08-28 13:54 ` Bob Rossi
2007-08-28 15:05 ` Gordon Prieur
2007-08-28 11:54 ` Nick Roberts
2007-08-28 12:40 ` Bob Rossi
2007-08-29 5:03 ` Nick Roberts
2007-08-30 21:10 ` Mark Kettenis
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=77356E57-639F-4F6B-B39E-4395D6FC8B87@apple.com \
--to=jingham@apple.com \
--cc=Gordon.Prieur@Sun.COM \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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