public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@us.ibm.com>
To: Andrew Burgess <aburgess@redhat.com>,
	Carl Love via Gdb-patches <gdb-patches@sourceware.org>,
	will schmidt <will_schmidt@vnet.ibm.com>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Subject: RE: [PATCH] Fix for gdb.base/break-idempotent.exp
Date: Wed, 29 Jun 2022 08:34:17 -0700	[thread overview]
Message-ID: <54294fecf3baf625715a5748827948f86d657234.camel@us.ibm.com> (raw)
In-Reply-To: <87zghvdc4v.fsf@redhat.com>

Andrew:

Thanks for letting me know.  I did a fresh pull, build and test to
verify everything looks good on my system.

Thanks for the help getting this fixed.  

               Carl 

On Wed, 2022-06-29 at 10:58 +0100, Andrew Burgess wrote:
> Carl Love via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> > Andrew:
> > 
> > Thanks for looking at the patch.  I am fine with you using your
> > patch
> > and merging in anything from mine that is useful.  Thanks for
> > sharing
> > you insight on the issues.  Thanks for the help in getting this
> > fixed.
> 
> Carl,
> 
> I pushed the patch below.
> 
> Thanks,
> Andrew
> 
> ---
> 
> commit 13f72372413400410aaa94b7f0e2ff7de663fdcb
> Author: Carl Love <cel@us.ibm.com>
> Date:   Wed Jun 22 16:14:20 2022 +0100
> 
>     gdb/testsuite: fix gdb.base/break-idempotent.exp on ppc
>     
>     When running the gdb.base/break-idempotent.exp test on ppc, I was
>     seeing some test failures (or rather errors), that looked like
> this:
>     
>       (gdb) watch local
>       Hardware watchpoint 2: local
>     
>       has_hw_wp_support: Hardware watchpoint detected
>       ERROR: no fileid for gcc2-power8
>       ERROR: Couldn't send delete breakpoints to GDB.
>       ERROR OCCURED: can't read "gdb_spawn_id": no such variable
>           while executing
>       "expect {
>       -i 1000 -timeout 100
>               -re ".*A problem internal to GDB has been detected" {
>                   fail "$message (GDB internal error)"
>                   gdb_internal_erro..."
>           ("uplevel" body line 1)
>           invoked from within
>     
>     What happens is that in break-idempotent.exp we basically do
> this:
>     
>         if {[prepare_for_testing "failed to prepare" $binfile
> $srcfile $opts]} {
>             continue
>         }
>     
>         # ....
>     
>         if {![skip_hw_watchpoint_tests]} {
>             test_break $always_inserted "watch"
>         }
>     
>     The problem with this is that skip_hw_watchpoint_tests, includes
> this:
>     
>         if { [istarget "i?86-*-*"]
>              || [istarget "x86_64-*-*"]
>              || [istarget "ia64-*-*"]
>              || [istarget "arm*-*-*"]
>              || [istarget "aarch64*-*-*"]
>              || ([istarget "powerpc*-*-linux*"] &&
> [has_hw_wp_support])
>              || [istarget "s390*-*-*"] } {
>             return 0
>         }
>     
>     For powerpc only we call has_hw_wp_support.  This is a caching
> proc
>     that runs a test within GDB to detect if we have hardware
> watchpoint
>     support or not.
>     
>     Unfortunately, to run this test we restart GDB, and when the test
> has
>     completed, we exit GDB.  This means that in break-idempotent.exp, 
> when
>     we call skip_hw_watchpoint_tests for the first time on powerpc,
> GDB
>     will unexpectedly be exited.  When we later call
> delete_breakpoints we
>     see the errors I reported above.
>     
>     The fix is to call skip_hw_watchpoint_tests early, before we
> start GDB
>     as part of the break-idempotent.exp script, and store the result
> in a
>     variable, we can then check this variable in the script as
> needed.
>     
>     After this change break-idempotent.exp runs fine on powerpc.
>     
>     Co-authored-by: Andrew Burgess <aburgess@redhat.com>
> 
> diff --git a/gdb/testsuite/gdb.base/break-idempotent.exp
> b/gdb/testsuite/gdb.base/break-idempotent.exp
> index 29002f103a8..837ac000b57 100644
> --- a/gdb/testsuite/gdb.base/break-idempotent.exp
> +++ b/gdb/testsuite/gdb.base/break-idempotent.exp
> @@ -36,6 +36,12 @@
> 
>  standard_testfile
> 
> +# The skip_hw_watchpoint_tests starts GDB on a small test program to
> +# check if HW watchpoints are supported.  We do not want to restart
> +# GDB after this test script has itself started GDB, so call
> +# skip_hw_watchpoint_tests first and cache the result.
> +set skip_hw_watchpoint_tests_p [skip_hw_watchpoint_tests]
> +
>  # Force a breakpoint re-set in GDB.  Currently this is done by
>  # reloading symbols with the "file" command.
> 
> @@ -174,7 +180,7 @@ foreach_with_prefix pie { "nopie" "pie" } {
>  	    test_break $always_inserted "hbreak"
>  	}
> 
> -	if {![skip_hw_watchpoint_tests]} {
> +	if {!$skip_hw_watchpoint_tests_p} {
>  	    test_break $always_inserted "watch"
>  	}
> 
> 


      reply	other threads:[~2022-06-29 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 22:38 Carl Love
2022-06-22 15:11 ` Carl Love
2022-06-27 13:40 ` Andrew Burgess
2022-06-27 15:14   ` Carl Love
2022-06-29  9:58     ` Andrew Burgess
2022-06-29 15:34       ` Carl Love [this message]

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=54294fecf3baf625715a5748827948f86d657234.camel@us.ibm.com \
    --to=cel@us.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=will_schmidt@vnet.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).