public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Luis Machado <luis.machado@arm.com>, gdb-patches@sourceware.org
Subject: Re: [pushed] [gdb/testsuite] Use maint ignore-probes in gdb.base/longjmp.exp
Date: Wed, 8 Feb 2023 16:38:14 +0100	[thread overview]
Message-ID: <d6885a04-b6c8-1343-3198-8ef1e0625265@suse.de> (raw)
In-Reply-To: <57277a06-0a9c-e731-beee-1f6d0e88ea6f@arm.com>

On 2/8/23 15:51, Luis Machado wrote:
> On 2/8/23 14:48, Tom de Vries wrote:
>> On 2/8/23 14:27, Luis Machado wrote:
>>> Hi Tom,
>>>
>>> Is the entire test supposed to PASS? I'm seeing the following on my 
>>> aarch64/Ubuntu 22.04 setup:
>>>
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 2: next over 
>>> call_longjmp (the program is no longer running)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 2: next over 
>>> setjmp (the program is no longer running)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 2: setup: 
>>> breakpoint at pattern start (got interactive prompt)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 2: setup: 
>>> breakpoint at safety net (got interactive prompt)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 2: setup: continue 
>>> to breakpoint at pattern start (the program exited)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 3: next over 
>>> pattern (the program is no longer running)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 3: setup: 
>>> breakpoint at pattern start (got interactive prompt)
>>> FAIL: gdb.base/longjmp.exp: with_probes=0: pattern 3: setup: continue 
>>> to breakpoint at pattern start (the program is no longer running)
>>>
>>> Maybe something is genuinely broken for aarch64 though, or I'm 
>>> missing some packages/debuginfo.
>>
>> Hi,
>>
>> I just ran this test-case on openSUSE Leap 15.4 aarch64, no problems 
>> found.
>>
> 
> Alright. That's good to know.

FWIW, I've tried this test-case also on various x86_64 distros other 
than the usual openSUSE Leap 15.4: ubuntu 20.04, fedora 37 and opensuse 
tumbleweed, again no problems found.

Thanks,
- Tom


  reply	other threads:[~2023-02-08 15:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 12:46 Tom de Vries
2023-02-08 13:27 ` Luis Machado
2023-02-08 14:48   ` Tom de Vries
2023-02-08 14:51     ` Luis Machado
2023-02-08 15:38       ` Tom de Vries [this message]
2023-02-08 18:06         ` Luis Machado
2023-02-08 20:36           ` Tom de Vries
2023-02-09 10:37             ` Luis Machado
2023-02-09 11:58               ` Luis Machado
2023-02-09 12:19                 ` Tom de Vries
2023-02-09 14:34                   ` Luis Machado
2023-02-09 16:44                     ` Luis Machado
2023-02-10 11:09                       ` Tom de Vries

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=d6885a04-b6c8-1343-3198-8ef1e0625265@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.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).