From: Mark Kettenis <kettenis@sibelius.xs4all.nl>
To: jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Don't apply line-number tweaks for non-GCC compilers
Date: Mon, 20 Sep 2004 22:00:00 -0000 [thread overview]
Message-ID: <200409202159.i8KLxTvs041757@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <vt2mzzkipj2.fsf@zenia.home> (message from Jim Blandy on 20 Sep 2004 16:44:33 -0500)
From: Jim Blandy <jimb@redhat.com>
Date: 20 Sep 2004 16:44:33 -0500
[ That earned you a nice bounce I suppose. I've moved, and therefore
got rid of my cable. On the bright side, I've now got a decent ISP
and a fixed IP address. ]
Mark Kettenis <kettenis@chello.nl> writes:
> The line-number tweaks we do for the sake of GCC 2.95.3 mess up the
> line number info for non-GCC compilers that emit stabs. In particular
> this makes it annoying to debug code using the Sun compilers on SPARC.
> This patch attempts to fix that. Please refer to the comment in the
> code for details.
>
> I deliberately did not remove the while line-number hack. In the end
> that's what we should really do, but I still do most of my GDB work on
> systems that have GCC 2.95.3 as their default compiler, and I really
> like being able to run the testsuite on those platforms.
>
> OK?
(Thanks for finding this, Andrew.)
Is there any reason you're not testing processing_gcc_compilation,
instead of checking the last N_FUN's desc?
Other than that it's a global variable? No not really. I suppose it
was because the patch actually is a slimmed down version of a patch
that tried (and failed) to distinguish between a broken GCC and a
fixed GCC too.
Do you prefer checking processing_gcc_compilation? I suppose it's
better because it makes the intent clearer.
Mark
next prev parent reply other threads:[~2004-09-20 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 15:03 Mark Kettenis
2004-09-14 20:05 ` Andrew Cagney
2004-09-20 21:46 ` Jim Blandy
2004-09-20 22:00 ` Mark Kettenis [this message]
2004-09-20 22:25 ` Jim Blandy
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=200409202159.i8KLxTvs041757@elgar.sibelius.xs4all.nl \
--to=kettenis@sibelius.xs4all.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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