Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mario Emmenlauer <mario@emmenlauer.de>
To: "Dr. Rolf Jansen" <rj@surtec.com>
Cc: gdb@sourceware.org
Subject: Re: gdb supported on powerpc-apple-darwin ?
Date: Sat, 16 Aug 2008 23:27:00 -0000	[thread overview]
Message-ID: <48A6FBFB.5010202@emmenlauer.de> (raw)
In-Reply-To: <958EAB4C-D513-4823-9111-25A6F5743307@surtec.com>


Hi Rolf,

Dr. Rolf Jansen wrote:
> Am 16.08.2008 um 11:44 schrieb Mario Emmenlauer:
> 
>> BTW: Apple developers: is the current (and upcoming) Apple gdb
>> still based on gdb's 2005 code?
> 
> Apple gdb has been forked from GNU gdb 6.3.50-20050815. And the current 
> version shipped with Xcode 3.1 is (Apple version gdb-960). The lates 
> version that can be downloaded at Apples OS site is gdb-961.

Is 961 the commit- (i.e. change-)number? Or does it correspond to
another way of labeling releases?


> The term "still based" in your question implies too much. Apple forked 
> GDB in 2005 and since then it became a different product, there a so 
> many (well documented) additions since then, that it cannot simply be 
> based on a newer FSF gdb. In fact that would mean to fork it again.

I see. But is there an information exchange going on?


>> I could not find newer commits in
>> the Changelog of gdb-908, are they just undocumented?
> 
> Look at:
> 
> <http://www.opensource.apple.com/darwinsource/iPhoneSDKBeta8/gdb-961/>

I was indeed missing 'ChangeLog-Apple', because it does not exist in
the root directory of gdb-908 (which was the newest release I could
find on the Mac developer pages). I'm sorry for the confusion, it
seems there is some active development going on.


>> Which version of FSF gdb does gdb-908 compare to?
> 
> Compare in which respect? Which features are you looking for?

The question was based on the assumption that there is a common patch
base on both forks. If the information exchange is little, it does not
make sense to try to compare.

I'm not actually missing a specific feature. I have rather experienced
bad performance and integration with my favorite GUI, using the mi
(actually mi2, I believe) interface. I read that the Apple fork is not
completely compatible in respect to this interface, for the sake of
better Xcode integration, which made me hope the FSF gdb would work
better.

Is there a compatibility mode for the Apple fork?

Cheers,

    Mario


  reply	other threads:[~2008-08-16 16:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 16:11 Mario Emmenlauer
2008-08-16 17:37 ` Daniel Jacobowitz
2008-08-16 22:07   ` Mario Emmenlauer
2008-08-17 12:32     ` Stan Shebs
2008-08-16 17:51 ` Stan Shebs
2008-08-16 21:59 ` Dr. Rolf Jansen
2008-08-16 23:27   ` Mario Emmenlauer [this message]
     [not found]     ` <70C46A91-B195-4AAA-9EB9-7D97B93A4519@surtec.com>
2008-08-17 14:56       ` Mario Emmenlauer
2008-08-16 23:40   ` Stan Shebs
2008-08-17 14:54     ` Mario Emmenlauer
2008-08-17 17:00       ` Stan Shebs
2008-08-17 22:57         ` Robert Dewar
2008-08-18 10:21           ` Mario Emmenlauer
2008-08-18 12:42             ` Robert Dewar
2008-08-18 17:52           ` Stan Shebs
2008-08-18 17:55             ` Robert Dewar
2008-08-18 22:15     ` Michael Snyder

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=48A6FBFB.5010202@emmenlauer.de \
    --to=mario@emmenlauer.de \
    --cc=gdb@sourceware.org \
    --cc=rj@surtec.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