Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Cc: Andrew Cagney <cagney@gnu.org>,
	Michael Chastain <mec.gnu@mindspring.com>
Subject: Re: [PATCH] Fixes testsuit/gdb.base/annota1.exp
Date: Wed, 22 Sep 2004 16:56:00 -0000	[thread overview]
Message-ID: <200409220953.53052.pgilliam@us.ibm.com> (raw)
In-Reply-To: <4151851B.1040100@gnu.org>

Andrew,

Thanks for your comments.  See below...

On Wednesday 22 September 2004 06:58, Andrew Cagney wrote:
> > On powerpc64--linux, annota1.exp has two problems:
> >
> > 1) A breakpoint in a shared object may be 'delayed'.  This changes GDB's
> > responce: both when the breakpoint is set and when it is hit.
>
> I'm not sure what you mean.  On i386 GNU/Linux, annota1.exp gets zero
> fails so this would suggest some sort of ISA specific bug?

The problem is specific to any ISA that uses delayed breakpoints...  I think 
that's just the Power64.  

>
> I see this lets GDB accept the ``warning: adjusting breakpoint''
> message.  I'm wondering if GDB should even emit the warning - it and the
> descriptor are very much integral parts of the ABI - and hence should be
> trying to always display the descriptor symbol and code address (and not
> display the dot symbol).

I think I agree.  Unless this level of detail is needed by the user for some 
reason.  And I don't think they need to be reminded every time the breakpoint 
is hit.  But that's the way the code is.  The testsuite should reflect the 
way the code is, and to a certain extent, the way it was.

>
> What's going to happen when 64-bit PPC stops emiting those dot symbols?

When this happens, then the regexp that I added would never be matched.  So 
Its kind of self correcting.  Some time later we can just remove the regexp.

>
> > 2) Due to a bug (I which I knew the number), GDB 'skids' past the
> > top-of-stack when doing a backtrace.  This causes two extra and severial
> > garbage stack frames to be displayed, eventually getting an error.
>
> You mean backtracing past main - that code was recently rewritten.
> However, there's apparently no test case for the feature, perhaphs it it
> should first be added and fixed?.  Anyway, I don't think we should be
> passing a broken backtrace.
>

Well... this doesn't 'pass' a broken backtrace, it just doesn't let a broken 
backtrace stop it from testing what it is really interested in: annotations.

I agree that we need a test for the 'backtracing past main' problem.  I will 
post one later today, along with a log showing it in action.  Which .exp file 
would you suggest I use as a model?

-=# Paul #=-

> Andrew
>

> > I have attached three patches: seperate patches for these two problems
> > and one patch that fixes them both.  I have also attached test logs so
> > you can see what's up.
> >
> > Ok to commit? (which one(s)?)
> >
> > -=# Paul #=-
> >
> > PS:  I thought the 'skidding past top-of-stack' problem was fixed.  But
> > it doesn't seem to be in cvs-main as of last week sometime.


  reply	other threads:[~2004-09-22 16:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 21:43 Paul Gilliam
2004-09-22 14:01 ` Andrew Cagney
2004-09-22 16:56   ` Paul Gilliam [this message]
2004-09-22 19:54     ` Andrew Cagney
2004-09-23  2:13       ` Paul Gilliam
2004-09-23 17:08         ` Michael Chastain
2004-09-23 17:25         ` Michael Chastain
2004-09-24 22:38         ` Test "set backtrace ..."; " Andrew Cagney
2004-09-23 17:25 ` Michael Chastain
2005-04-07 17:27 Paul Gilliam
2005-04-14 19:36 ` Daniel Jacobowitz
2005-04-15 23:38   ` Paul Gilliam
2005-04-27 15:49     ` Daniel Jacobowitz
2005-04-27 20:02       ` Paul Gilliam

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=200409220953.53052.pgilliam@us.ibm.com \
    --to=pgilliam@us.ibm.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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