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

Mario Emmenlauer wrote:
> 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?
I got it to where it would up seize up waiting for signals and such from 
the inferior. :-) Just that much involved bringing over several thousand 
lines of Darwin-specific code. Dunno when/if I'll get back to it, 
CodeSourcery is keeping me plenty busy. :-)
>
> 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)?
That's exactly what I did. The problem is that basic Darwin support is 
more complicated than average for a native config, because one has to 
listen for both messages and signals delivered by the system, and some 
of those calls are blocking - so GDB itself has to be multithreaded just 
so it can simultaneously listen for everything.

A concerted effort by one person (either inside or outside Apple) could 
probably get the two versions back in sync, but it's a heavy-duty 
hacking project that will likely take a number of months of fulltime effort.

Stan


  reply	other threads:[~2008-08-16 23:27 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
2008-08-17 17:00       ` Stan Shebs [this message]
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=48A76233.4090201@earthlink.net \
    --to=stanshebs@earthlink.net \
    --cc=gdb@sourceware.org \
    --cc=mario@emmenlauer.de \
    --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