From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>,
Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] import drow dbxread.c fix to branch
Date: Wed, 03 Apr 2002 22:01:00 -0000 [thread overview]
Message-ID: <20020404010112.A13460@nevyn.them.org> (raw)
In-Reply-To: <200204040536.g345a6t30923@duracef.shout.net>
On Wed, Apr 03, 2002 at 11:36:06PM -0600, Michael Elizabeth Chastain wrote:
> DanielJ writes:
> > Only shows on GCC 3.1, eh? I'll try to look at it later, but I have no
> > post-3.0 toolchain installed right now. Actually, I should
> > investigate, to make sure it isn't a 3.1 regression...
>
> On the next spin, I'll make a special report of regressions for gcc
> 3.0.4 versus gcc-3_1-branch. You can already look at "difference by gcc"
> in the regular report if you want to pick up a hot spot or two.
>
> BTW my test harness now saves the whole test directory, including all
> the executable files. In fact I'll just throw some tarball up in my
> ftp directory in case it might help someone:
>
> ftp://ftp.shout.net/pub/users/mec/gdb/for-pr-gdb-381.tar.gz
> ftp://ftp.shout.net/pub/users/mec/gdb/for-pr-gdb-381-src.tar.gz
Thanks. It does help - that was pretty easy, actually :). I've found
the bug; mi-cmd-disassemble does not recognize '0' line numbers, and it
needs to. I don't know why only 3.1 triggers this. Probably a
function padding thing; the end of the previous function seems to share
a PC with the beginning of the one being listed. Here's a patch;
Andrew, how's this look?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
2002-04-04 Daniel Jacobowitz <drow@mvista.com>
* mi-cmd-disas.c (mi_cmd_disassemble): Skip end-of-function
markers in the line table.
Index: mi/mi-cmd-disas.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-cmd-disas.c,v
retrieving revision 1.12
diff -u -p -r1.12 mi-cmd-disas.c
--- mi-cmd-disas.c 2002/01/05 04:30:46 1.12
+++ mi-cmd-disas.c 2002/04/04 05:59:51
@@ -332,6 +332,10 @@ mi_cmd_disassemble (char *command, char
&& le[i].pc == le[i + 1].pc)
continue; /* Ignore duplicates */
+ /* Skip any end-of-function markers. */
+ if (le[i].line == 0)
+ continue;
+
mle[newlines].line = le[i].line;
if (le[i].line > le[i + 1].line)
out_of_order = 1;
next prev parent reply other threads:[~2002-04-04 6:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 21:36 Michael Elizabeth Chastain
2002-04-03 22:01 ` Daniel Jacobowitz [this message]
2002-04-04 10:58 ` Andrew Cagney
2002-04-04 11:33 ` Elena Zannoni
2002-04-04 11:40 ` Daniel Jacobowitz
2002-04-04 12:15 ` Elena Zannoni
2002-04-04 12:24 ` Daniel Jacobowitz
2002-04-04 12:18 ` Andrew Cagney
2002-04-04 12:20 ` Daniel Berlin
2002-04-04 12:30 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 13:34 Michael Elizabeth Chastain
2002-04-04 18:17 Michael Elizabeth Chastain
2002-04-04 18:36 ` Daniel Jacobowitz
2002-04-04 19:35 ` Elena Zannoni
2002-04-05 13:10 ` Jim Blandy
2002-04-05 13:16 ` Daniel Jacobowitz
2002-04-04 8:37 Michael Elizabeth Chastain
2002-04-03 20:48 Michael Elizabeth Chastain
2002-04-03 21:09 ` Daniel Jacobowitz
2002-04-01 21:36 Michael Elizabeth Chastain
2002-04-01 21:43 ` Eli Zaretskii
2002-04-03 19:43 ` Andrew Cagney
2002-04-01 11:22 Michael Elizabeth Chastain
2002-04-01 20:49 ` Eli Zaretskii
2002-04-01 8:56 Michael Elizabeth Chastain
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=20020404010112.A13460@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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