From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
David Carlton <carlton@math.stanford.edu>,
Andrew Cagney <ac131313@redhat.com>,
gdb-patches@sources.redhat.com, jjohnstn@redhat.com
Subject: Re: PATCH RFA: Fix MI stack frame output for synthetic frames
Date: Wed, 05 Feb 2003 14:54:00 -0000 [thread overview]
Message-ID: <15937.9876.260141.789359@localhost.redhat.com> (raw)
In-Reply-To: <20030205135947.GA30516@nevyn.them.org>
Daniel Jacobowitz writes:
> On Wed, Feb 05, 2003 at 12:24:16AM -0800, Jason Molenda wrote:
> > gcc 3.2 is outputting debug info like this -
> >
> > .stabs "subroutine:F(9,7)",36,0,0,subroutine
> > .stabs "in:p(0,1)",160,0,0,8
> > .globl subroutine
> > .type subroutine,@function
> > subroutine:
> > .stabn 68,0,48,.LM18-subroutine
> > .LM18:
> > pushl %ebp
> > movl %esp, %ebp
> > nop
> > .stabn 68,0,49,.LM19-subroutine ; line #49 is the while (...)
> > .LM19:
> > .L6:
> > cmpl $99, 8(%ebp)
> > jle .L8
> > jmp .L5
> > .L8:
> >
> > The compiler is correct to put the line stab there (it does the
> > equivalent for DWARF2), and gdb is correct in putting the breakpoint
> > on the cmpl insn, but the unfortunate end result of these two is that
> > a user putting a breakpoint on the subroutine will have a breakpoint
> > that's tripped each iteration of the loop.
> >
> > Given all that, I'll check in a change to mi-syn-frames.c so this
> > function reads
> >
> > void
> > subroutine (int in)
> > {
> > int count = in;
> > while (count < 100)
> > count++;
> > }
> >
> > The assignment gives us two assembly instructions after the end of the
> > prologue for a breakpoint that won't be hit at each iteration. It's
> > stupid, I know.
> >
> > I'll make that change and run it through the testsuites tomorrow
> > night. If I get approval for the change before then (hint hint :)
> > I'll check it in, else I'll post a patch.
>
> Pre-approved as an obvious fix to the test. Thanks for following up.
> I think there are a few other failures; I'll check again after you've
> fixed this one.
As one of the MI testsuite maintainers, I'll approve the patch, but, Jason
can you post when you do the check in?
elena
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-05 14:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 14:22 PATCH: " Jason Molenda
2002-11-08 14:38 ` Andrew Cagney
2002-11-08 14:46 ` Jason Molenda
2002-11-08 15:56 ` Andrew Cagney
2002-11-09 0:47 ` PATCH RFA: " Jason Molenda
2002-11-09 2:13 ` Jason Molenda
2002-11-15 11:16 ` Ping on two MI patches Jason Molenda
2003-02-02 5:52 ` PATCH RFA: Fix MI stack frame output for synthetic frames Andrew Cagney
2003-02-02 17:38 ` Mark Kettenis
2003-02-02 18:23 ` Andrew Cagney
2003-02-02 20:51 ` Mark Kettenis
2003-02-03 18:15 ` David Carlton
2003-02-03 18:27 ` Jason Molenda
2003-02-03 18:34 ` Daniel Jacobowitz
2003-02-04 8:09 ` Jason Molenda
2003-02-05 8:28 ` Jason Molenda
2003-02-05 13:59 ` Daniel Jacobowitz
2003-02-05 14:54 ` Elena Zannoni [this message]
2003-02-06 6:28 ` Fix committed for mi-syn-frames fails (was: Re: PATCH RFA: Fix MI stack frame output for synthetic frames) Jason Molenda
2003-02-06 6:31 ` Jason Molenda
2003-02-06 17:01 ` David Carlton
2003-02-06 18:21 ` Andrew Cagney
2003-02-06 18:27 ` Jason Molenda
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=15937.9876.260141.789359@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jason-swarelist@molenda.com \
--cc=jjohnstn@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