Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mario Emmenlauer <mario@emmenlauer.de>
To: Stan Shebs <stan@codesourcery.com>
Cc: "Dr. Rolf Jansen" <rj@surtec.com>, gdb@sourceware.org
Subject: Re: gdb supported on powerpc-apple-darwin ?
Date: Sun, 17 Aug 2008 14:54:00 -0000	[thread overview]
Message-ID: <48A74D74.5040707@emmenlauer.de> (raw)
In-Reply-To: <48A71019.7060503@codesourcery.com>


Hi Stan,

Stan Shebs wrote:
> 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.
>>
>> 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.
> "Forked GDB in 2005" is not quite accurate. Apple has had its own 
> version of GDB for many many years (going back to NeXT days I believe), 
> and has merged FSF GDB code into it a number of times, the most recent 
> being the one I did in 2005. Apple has also contributed code to FSF GDB 
> a number of times, both directly and indirectly. A new merge at this 
> point would be rather painful (and now there is a GPLv3 issue to boot), 
> and so it's been getting put off. Basic Darwin support in FSF GDB would 
> make it a lot easier though, one of the reasons I made a pass at it.

I would assume that basic Darwin support in FSF GDB would be a good
starting point. You mentioned you already put some work into it, any
chances that you will continue? How far have you gotten?

It seems very sadening that FSF gdb won't ever incorporate Apples
changes (or another type of darwin support). Of course one might know
who to point the finger at, but in the end that won't help.
If Apples fork is GPL, would it not be possible to back-merge the
darwin support, leaving out the other changes that are incompatible
to the current interface(s)?

Cheers,

    Mario


  reply	other threads:[~2008-08-16 21:59 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
     [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 [this message]
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=48A74D74.5040707@emmenlauer.de \
    --to=mario@emmenlauer.de \
    --cc=gdb@sourceware.org \
    --cc=rj@surtec.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