public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/30387] gdbserver assert error on arm platform
Date: Fri, 11 Aug 2023 16:45:34 +0000	[thread overview]
Message-ID: <bug-30387-4717-kR8iLMtfNx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30387-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30387

Luis Machado <luis.machado at arm dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #21 from Luis Machado <luis.machado at arm dot com> ---
Hi,

Thanks for the patch.

A few comments.

When running this test on a 32-bit docker instance in 64-bit hardware, against
the native-gdbserver board, I'm seeing FAIL's:

# of expected passes            3074
# of unexpected failures        13

The FAIL's are of this kind:

FAIL: gdb.threads/next-fork-exec-other-thread.exp: fork_func=fork:
target-non-stop=on: non-stop=off: displaced-stepping=off: i=0: next to other
line

They fail for both a patched and an unpatched gdb. But I see 12 unexpected core
files for the unpatched gdb.

It passes for both patched and unpatched native gdb though. So it might not be
exercising the bug there.

Also, I gave the testcase a try, and I noticed it takes a reasonably long time
to run, both on 32-bit and 64-bit.

Is it a timing issue of some kind that we need a lot of iterations to run to
get it to show up?

From the testcase description, it looks like this is mostly a software
single-step issue and on gdbserver. Should we isolate the tests to gdbserver
and known targets using software single-step instead of making all targets run
the test only to potentially PASS every time?

So, in summary:

* For native gdb (32-bit or 64-bit), this doesn't seem to be exercising the
bug.

* For native-gdbserver on 64-bit, it doesn't seem to exercise the bug.

* For native-gdbserver on 32-bit, I see unexpected core files, which indicates
it does exercise the bug, but I also see unexpected failures, which may be
something off with the testcase patterns.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-11 16:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  6:43 [Bug gdb/30387] New: " 2982971635 at qq dot com
2023-04-25  6:54 ` [Bug gdb/30387] " 2982971635 at qq dot com
2023-04-25  6:55 ` 2982971635 at qq dot com
2023-04-25  7:01 ` 2982971635 at qq dot com
2023-04-25  7:02 ` 2982971635 at qq dot com
2023-05-02  7:11 ` luis.machado at arm dot com
2023-05-02 14:17 ` [Bug server/30387] " luis.machado at arm dot com
2023-05-04  9:17 ` 2982971635 at qq dot com
2023-05-04 10:45 ` luis.machado at arm dot com
2023-05-05  2:20 ` 2982971635 at qq dot com
2023-05-05  2:22 ` 2982971635 at qq dot com
2023-05-10  7:41 ` 2982971635 at qq dot com
2023-05-10  7:52 ` luis.machado at arm dot com
2023-05-10  7:52 ` luis.machado at arm dot com
2023-05-10  9:16 ` 2982971635 at qq dot com
2023-05-11  1:56 ` simon.marchi at polymtl dot ca
2023-05-11  2:50 ` 2982971635 at qq dot com
2023-06-07 10:24 ` 2982971635 at qq dot com
2023-07-05 14:25 ` brobecker at gnat dot com
2023-07-05 14:33 ` luis.machado at arm dot com
2023-07-05 15:21 ` brobecker at gnat dot com
2023-08-08  2:59 ` kevinb at redhat dot com
2023-08-11 16:45 ` luis.machado at arm dot com [this message]
2023-08-11 17:33 ` kevinb at redhat dot com
2023-08-11 17:59 ` luis.machado at arm dot com
2023-08-12  2:38 ` kevinb at redhat dot com
2023-08-12  3:54 ` cvs-commit at gcc dot gnu.org
2023-08-12  4:02 ` kevinb at redhat dot com

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=bug-30387-4717-kR8iLMtfNx@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).