public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@redhat.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 03/11] Change gdb.base/skip-solib.exp deal with lack of epilogue information
Date: Mon, 7 Mar 2022 16:53:10 -0300	[thread overview]
Message-ID: <e95baffc-2096-6cd0-b84a-511b4aac5fbc@redhat.com> (raw)
In-Reply-To: <76afd937-0202-9bde-aee1-c8f3f1119777@palves.net>

On 3/2/22 13:17, Pedro Alves wrote:
> On 2022-01-26 19:50, Bruno Larsen via Gdb-patches wrote:
>> When testing with clang, this feature worked, but the test failed
>> because it checked specifically to see if we were at the main function.
>> Without epilogue information, the inferior would be at libc_start_main
>> (or equivalent) instead. Having this test changed would allows us to
>> identify if the test stops working for real at some point.
> 
> I'm having trouble understanding what you're saying.  I wonder whether
> pasting a snippet of the failing case would help?
> 
>> ---
>>   gdb/testsuite/gdb.base/skip-solib.exp | 11 +++++++++--
>>   1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/gdb/testsuite/gdb.base/skip-solib.exp b/gdb/testsuite/gdb.base/skip-solib.exp
>> index ce2b080229e..99833533b6a 100644
>> --- a/gdb/testsuite/gdb.base/skip-solib.exp
>> +++ b/gdb/testsuite/gdb.base/skip-solib.exp
>> @@ -82,7 +82,7 @@ with_test_prefix "ignoring solib file" {
>>       # We shouldn't step into square(), since we skipped skip-solib-lib.c.
>>       #
>>       gdb_test "step" ""
>> -    gdb_test "bt" "#0\\s+main.*"
>> +    gdb_test "bt 1" "#0.*main.*"
> 
> Is the tweak here to change the regexp to match both "main" and "libc_start_main"?

Sorry about the confusing commit message. Yes, this was the plan. Essentially, the test was failing because we dropped to libc_start_main and it expected to still be in main.

I have changed my mind on this approach, however. V2 should be coming shortly.

> 
>>   }
>>   
>>   #
>> @@ -114,5 +114,12 @@ with_test_prefix "ignoring solib function" {
>>       # the last line of square.
>>       #
>>       gdb_test "step" ""
>> -    gdb_test "bt" "#0\\s+square.*"
>> +    gdb_test_multiple "bt 1" "skipped multiply" {
>> +	-re "#0\\s+square.*" {
>> +	    pass "skipped multiply"
>> +	}
>> +	-re "#0.*main.*" {
>> +	    pass "skipped multiply"
>> +	}
>> +    }
>>   }
> 


-- 
Cheers!
Bruno Larsen


  reply	other threads:[~2022-03-07 19:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 19:50 [PATCH 00/11] gdb/testsuite: Cleanup gdb.base for clang testing Bruno Larsen
2022-01-26 19:50 ` [PATCH 01/11] change gdb.base/skip.exp to use finish instead of step Bruno Larsen
2022-02-25 17:00   ` Andrew Burgess
2022-03-02 16:11   ` Pedro Alves
2022-03-02 16:39     ` Andrew Burgess
2022-03-07 19:59       ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 02/11] change gdb.base/symbol-alias to xfail with clang Bruno Larsen
2022-01-26 19:50 ` [PATCH 03/11] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-03-02 16:17   ` Pedro Alves
2022-03-07 19:53     ` Bruno Larsen [this message]
2022-01-26 19:50 ` [PATCH 04/11] change gdb.base/nodebug.c to not fail with clang Bruno Larsen
2022-01-26 19:50 ` [PATCH 05/11] update gdb.base/info-program.exp " Bruno Larsen
2022-01-26 19:50 ` [PATCH 06/11] fix gdb.base/access-mem-running.exp for clang testing Bruno Larsen
2022-01-26 19:50 ` [PATCH 07/11] fix gdb.base/call-ar-st to work with clang Bruno Larsen
2022-03-02 18:59   ` Pedro Alves
2022-03-04 14:14     ` Tom Tromey
2022-03-07 20:39     ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 08/11] add xfails to gdb.base/complex-parts.exp when testing " Bruno Larsen
2022-03-02 19:10   ` Pedro Alves
2022-01-26 19:50 ` [PATCH 09/11] gdb/testsuite: don't test gdb.base/msym-bp-shl " Bruno Larsen
2022-03-02 19:33   ` Pedro Alves
2022-03-08 12:58     ` Bruno Larsen
2022-03-30 12:19     ` Bruno Larsen
2022-03-31 18:49       ` Pedro Alves
2022-03-31 19:13         ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 10/11] make use of finish to leave function in gdb.base/skip-inline.exp Bruno Larsen
2022-01-26 19:50 ` [PATCH 11/11] explicitly test for stderr in gdb.base/dprintf.exp Bruno Larsen
2022-03-02 16:50   ` Pedro Alves
2022-03-31 13:44     ` Bruno Larsen
2022-03-31 14:31       ` Pedro Alves
2022-02-09 12:03 ` [PING][PATCH 00/11] gdb/testsuite: Cleanup gdb.base for clang testing Bruno Larsen
2022-02-21 12:53   ` [PINGv2][PATCH " Bruno Larsen

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=e95baffc-2096-6cd0-b84a-511b4aac5fbc@redhat.com \
    --to=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).