Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Regression: Re: [PATCH] Fix some i386 unwinder inconcistencies
Date: Mon, 13 Jun 2011 10:49:00 -0000	[thread overview]
Message-ID: <20110613104911.GA1965@host1.jankratochvil.net> (raw)
In-Reply-To: <201106122057.p5CKvUEa030437@glazunov.sibelius.xs4all.nl>

On Sun, 12 Jun 2011 22:57:30 +0200, Mark Kettenis wrote:
> This diff fixes a few issues with the epilogue and stack tramp unwinders.
> 
> Committed.
> 
> 2011-06-12  Mark Kettenis  <kettenis@gnu.org>
>  
> 	* i386-tdep.c (i386_epilogue_frame_cache): Simplify code.  Call
> 	get_frame_func instead of get_frame_pc to determine the code
> 	address used to construct the frame ID.
> 	(i386_epilogue_frame_unwind_stop_reason): Fix coding style.
> 	(i386_epilogue_frame_this_id): Likewise.
> 	(i386_epilogue_frame_prev_register): New function.
> 	(i386_epilogue_frame_unwind): Use i386_epilogue_frame_prev_register.
> 	(i386_stack_tramp_frame_sniffer): Fix coding style.
> 	(i386_stack_tramp_frame_unwind): Use i386_epilogue_frame_prev_register.
> 	(i386_gdbarch_init): Fix comments.

On all the tested platforms Fedora-{13,14,15,Rawhide} for {i686,x86_64-m32}
(but not for x86_64):
-PASS: gdb.base/watchpoint-cond-gone.exp: Catch the no longer valid watchpoint
+FAIL: gdb.base/watchpoint-cond-gone.exp: Catch the no longer valid watchpoint
-XFAIL: gdb.mi/mi-watch.exp: sw: watchpoint trigger (stopped at wrong place)
+XFAIL: gdb.mi/mi-watch.exp: sw: watchpoint trigger (unknown output after running)
-XFAIL: gdb.mi/mi2-watch.exp: sw: watchpoint trigger (stopped at wrong place)
+XFAIL: gdb.mi/mi2-watch.exp: sw: watchpoint trigger (unknown output after running)

due to: commit b304e1f3bb4fee38d829dbd85ea3c0f43399aa7c

This is a regression.

The regressions are all just instances of:

 finish
 Run till exit from #0  func () at ./gdb.base/watchpoint-cond-gone.c:26
-
-Watchpoint 3 deleted because the program has left the block in
-which its expression is valid.
+Error evaluating expression for watchpoint 3
+can't compute CFA for this frame
+Watchpoint 3 deleted.
 0x080483e0 in func () at ./gdb.base/watchpoint-cond-gone.c:28
 28     }
-(gdb) PASS: gdb.base/watchpoint-cond-gone.exp: Catch the no longer valid watchpoint
+(gdb) FAIL: gdb.base/watchpoint-cond-gone.exp: Catch the no longer valid watchpoint


Thanks,
Jan


  parent reply	other threads:[~2011-06-13 10:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-12 20:57 Mark Kettenis
2011-06-13  2:32 ` Yao Qi
2011-06-13 14:50   ` Mark Kettenis
2011-06-13 10:49 ` Jan Kratochvil [this message]
2011-06-13 15:37   ` Regression: " Mark Kettenis
2011-06-13 16:11     ` Jan Kratochvil
2011-06-13 19:10       ` Mark Kettenis
2011-06-13 20:46         ` Jan Kratochvil
2011-06-26  8:41   ` [patch 1/2] Code reformatting for patch 2/2 [Re: Regression: Re: [PATCH] Fix some i386 unwinder inconcistencies] Jan Kratochvil
2011-06-29 22:20     ` Jan Kratochvil
2011-06-26  8:42   ` [patch 2/2] Disable epilogue unwinders on recent GCCs " Jan Kratochvil
2011-06-27  9:39     ` Mark Kettenis
2011-06-28 20:02       ` Tom Tromey
2011-06-28 20:06         ` Jan Kratochvil
2011-06-29 22:26       ` Jan Kratochvil
2011-06-28 19:56     ` Tom Tromey

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=20110613104911.GA1965@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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