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: Sun, 17 Aug 2008 14:56:00 -0000 [thread overview]
Message-ID: <48A74F72.2010400@emmenlauer.de> (raw)
In-Reply-To: <70C46A91-B195-4AAA-9EB9-7D97B93A4519@surtec.com>
Hi,
Dr. Rolf Jansen wrote:
>>>> 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.
>
> Well you have three options:
>
> 1. if you favourite GUI is open source, then you can try
> to accomodate for the Apples mi dialect there.
Sadly, it isn't. But I called on the developers, lets see what happens.
> OR
>
> 2. you can add in the FSF mi into Apples GDB. This
> sounds more complicated than it is. I did this
> the other way around. I produced an mi for Xcode
> called miX and mixed it into the current FSF
> GDB. With that I can do cross platform debugging
> from within Xcode.
>
> <http://code.google.com/p/xcxdb/>
I saw your post in this regard, quite nice!
It seems a good starting point if I should decide to contribute
to gdb.
> To make a reasonable decision for 1 | 2 | 3, you might first want to
> figure out which MI commands are mis-understood by Apples-gdb or which
> MI results are mis-understood by your favourite GUI.
>
> For this you might want to let your GUI call gdb by the way of a proxy
> shell script. This shell script contains the following lines:
>
> #!/bin/sh
> tee ~/Desktop/gdb-session.in | /usr/bin/gdb --interp=mi2 | tee
> ~/Desktop/gdb-session.out
Thanks, this is indeed the first thing to do. I will check and see whats
going on between the GUI and gdb, and which commands exactly confuse
the former. I already know that these are few, so with some luck I
can even avoid them.
Cheers,
Mario
next prev parent reply other threads:[~2008-08-16 22:07 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 [this message]
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=48A74F72.2010400@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