Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	gdb-patches@sources.redhat.com, jjohnstn@redhat.com
Subject: Re: PATCH RFA: Fix MI stack frame output for synthetic frames
Date: Mon, 03 Feb 2003 18:15:00 -0000	[thread overview]
Message-ID: <ro17kchb58n.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3E3CB218.1020706@redhat.com>

On Sun, 02 Feb 2003 00:52:24 -0500, Andrew Cagney <ac131313@redhat.com> said:
>> [gdb/ChangeLog]
>> 2002-11-09  Jason Molenda  (jason-cl@molenda.com)
>> * stack.c (print_frame_info_base): Output complete FRAME tuple

>> for synthesized frames.
>> [gdb/testsuite/ChangeLog]

>> 2002-11-09  Jason Molenda  (jason-cl@molenda.com)
>> * gdb.mi/mi-syn-frame.exp: New tests for synthetic frames in

>> stack backtraces.
>> * gdb.mi/inferior-mischief.c: Part of same.
>> 

> I've (finally ...) tested it and checked it in.  (renamed
> inferior-mischief.c to mi-syn-frame.c though - booring).

> Passes fine on x86.  I suspect other targets won't be so lucky.

On i686-pc-linux-gnu/GCC3.1/DWARF2, I get the following:

Running ./gdb.mi/mi-syn-frame.exp ...
PASS: gdb.mi/mi-syn-frame.exp: breakpoint at main
PASS: gdb.mi/mi-syn-frame.exp: mi runto main
PASS: gdb.mi/mi-syn-frame.exp: 400-break-insert foo
PASS: gdb.mi/mi-syn-frame.exp: call inferior's function with a breakpoint set in it
PASS: gdb.mi/mi-syn-frame.exp: backtrace from inferior function stopped at bp, showing gdb dummy frame
PASS: gdb.mi/mi-syn-frame.exp: 403-exec-continue
PASS: gdb.mi/mi-syn-frame.exp: 404-stack-list-frames 0 0
PASS: gdb.mi/mi-syn-frame.exp: 405-break-insert subroutine
PASS: gdb.mi/mi-syn-frame.exp: 406-data-evaluate-expression have_a_very_merry_interrupt()
PASS: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames
FAIL: gdb.mi/mi-syn-frame.exp: 408-exec-continue
FAIL: gdb.mi/mi-syn-frame.exp: 409-stack-list-frames 0 0
FAIL: gdb.mi/mi-syn-frame.exp: call inferior function which raises exception
FAIL: gdb.mi/mi-syn-frame.exp: backtrace from inferior function at exception

I haven't investigated the failures at all.

David Carlton
carlton@math.stanford.edu


  parent reply	other threads:[~2003-02-03 18:15 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 [this message]
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
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=ro17kchb58n.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=ac131313@redhat.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