From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
Date: Sat, 09 Feb 2002 14:14:00 -0000 [thread overview]
Message-ID: <20020209171451.A28967@nevyn.them.org> (raw)
In-Reply-To: <npaduid3sr.fsf@zwingli.cygnus.com>
I assume so. But that patch went in, and I'd rather leave it in at
least until we have a policy about what not to display that goes across
all targets.
On Sat, Feb 09, 2002 at 11:21:24AM -0500, Jim Blandy wrote:
>
> If you apply my FRAME_CHAIN_VALID patch, doesn't that simply eliminate
> these failures altogether, since __libc_start_main doesn't appear in
> the backtrace?
>
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> > On Wed, Jan 09, 2002 at 07:06:28PM -0500, Daniel Jacobowitz wrote:
> > > >From the "annoying testsuite failures cleanup" department - if anyone has a
> > > bright idea on how to write annota tests in a more readable, less
> > > long-single-line fashion, I'd love to hear it. This fixes the test on all
> > > my compiler/debug combinations, i386-linux. OK to commit?
> >
> > Anyone?
> >
> > > 2002-01-09 Daniel Jacobowitz <drow@mvista.com>
> > >
> > > * gdb.base/annota1.exp (backtrace from shlibrary): Fix spelling.
> > > Allow a start function above main.
> > >
> > > Index: annota1.exp
> > > ===================================================================
> > > RCS file: /cvs/src/src/gdb/testsuite/gdb.base/annota1.exp,v
> > > retrieving revision 1.7
> > > diff -u -p -r1.7 annota1.exp
> > > --- annota1.exp 2001/12/20 16:52:07 1.7
> > > +++ annota1.exp 2002/01/09 23:53:35
> > > @@ -247,8 +247,8 @@ gdb_expect {
> > > #
> > > send_gdb "backtrace\n"
> > > gdb_expect {
> > > - -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0 \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1 \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n$gdb_prompt$" \
> > > - { pass "bactrace from shlibrary" }
> > > + -re "\r\n\032\032post-prompt\r\n\r\n\032\032frame-begin 0 $hex\r\n.0 \r\n(\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n)*\032\032frame-function-name\r\nprintf\r\n\032\032frame-args\r\n \\(.*frame-end\r\n\r\n\032\032frame-begin 1 $hex\r\n.1 \r\n\032\032frame-address\r\n$hex\r\n\032\032frame-address-end\r\n in \r\n\032\032frame-function-name\r\nmain\r\n\032\032frame-args\r\n \\(\\)\r\n\032\032frame-source-begin\r\n at \r\n\032\032frame-source-file\r\n${srcdir}/${subdir}/${srcfile}\r\n\032\032frame-source-file-end\r\n:\r\n\032\032frame-source-line\r\n.*\r\n\032\032frame-source-end\r\n\r\n\r\n\032\032frame-end\r\n(\r\n\032\032frame-begin .*\r\n\r\n\032\032frame-end\r\n)*$gdb_prompt$" \
> > > + { pass "backtrace from shlibrary" }
> > > -re ".*$gdb_prompt$" { fail "backtrace from shlibrary" }
> > > timeout { fail "backtrace from shlibrary (timeout)" }
> > > }
> > >
> >
> > --
> > Daniel Jacobowitz Carnegie Mellon University
> > MontaVista Software Debian GNU/Linux Developer
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-09 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 16:05 Daniel Jacobowitz
2002-01-09 16:41 ` Andrew Cagney
2002-01-29 21:57 ` Daniel Jacobowitz
2002-01-29 22:59 ` Kevin Buettner
2002-01-30 7:01 ` Fernando Nasser
2002-01-30 21:08 ` Daniel Jacobowitz
2002-02-09 8:19 ` Jim Blandy
2002-02-09 14:14 ` Daniel Jacobowitz [this message]
2002-01-30 8:02 Michael Elizabeth Chastain
2002-01-30 8:37 ` Fernando Nasser
2002-02-09 8:18 ` Jim Blandy
2002-02-09 8:19 ` 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=20020209171451.A28967@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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