Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb cvs vs x86_64-apple-darwin10
Date: Mon, 31 Aug 2009 18:11:00 -0000	[thread overview]
Message-ID: <20090831163835.GB12873@bromo.med.uc.edu> (raw)
In-Reply-To: <EE7552C5-3672-4F0C-BF46-D1078E039A68@adacore.com>

On Mon, Aug 31, 2009 at 03:33:08PM +0200, Tristan Gingold wrote:
>
> On Aug 31, 2009, at 3:22 PM, Jack Howarth wrote:
>> Tristan,
>>   Getting x86_64-apple-darwin10 working should be a higher priority
>> for gdb 7.0 since it sounds like after the VTA branch merge into gcc
>> 4.5, we will need to have access to gdb 7.0 to debug code generated
>> with gcc 4.5 on darwin.
>
> Hi,
>
> can you clarify your issue: is it Snow Leopard vs Leopard (as I thought 
> first)
> or is it fsf-gdb vs Apple gdb ?
>
> I might be wrong but VTA concerns only optimized code, so we will be  
> able to debug code generated
> without optimizations.
>
> Tristan.

Tristan,
   If you follow the thread starting at...

http://gcc.gnu.org/ml/gcc-patches/2009-08/msg01629.html

you will see other platforms like AIX are concerned as well.
The best answer I have read so far...

http://gcc.gnu.org/ml/gcc-patches/2009-08/msg01656.html

...suggests that FSF gcc will 'try' to maintain compatibility
in the generated debug code but may not go out of their way
to keep hacks to work around bugs in the older version of
gdb.
                Jack


      reply	other threads:[~2009-08-31 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  7:58 Jack Howarth
2009-08-31 13:10 ` Tristan Gingold
2009-08-31 13:29   ` Jack Howarth
2009-08-31 13:33     ` Jonas Maebe
2009-08-31 16:38       ` Jack Howarth
2009-08-31 16:20     ` Tristan Gingold
2009-08-31 18:11       ` Jack Howarth [this message]

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=20090831163835.GB12873@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.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