public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30074] FAIL: gdb.threads/schedlock.exp: schedlock=on: cmd=continue: stop all threads (with lock) (timeout)
Date: Sun, 05 Feb 2023 18:30:51 +0000	[thread overview]
Message-ID: <bug-30074-4717-4FeLjx54fE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30074-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
I think this is a problem of the processor running too fast, so this loop:
...
    /* Don't run forever.  Run just short of it :)  */
    while (*myp > 0)
      {
        /* schedlock.exp: main loop.  */
        MAYBE_CALL_SOME_FUNCTION(); (*myp) ++;
      }
...
just finishes and the thread exits. 

Increasing the amount of iterations by doing:
...
-    int *myp = (int *) &args[my_number];                                       
+    unsigned int *myp = (int *) &args[my_number];                             
                   ...
already seems to fix things (is the correct thing to do anyway, given that the
declared type of *args is unsigned int).

But I think a more structural fix is required, to make sure things will work
for an even faster processor.

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

  reply	other threads:[~2023-02-05 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 12:16 [Bug gdb/30074] New: " vries at gcc dot gnu.org
2023-02-05 18:30 ` vries at gcc dot gnu.org [this message]
2023-02-06 10:33 ` [Bug testsuite/30074] " vries at gcc dot gnu.org
2023-02-06 11:52 ` cvs-commit at gcc dot gnu.org
2023-02-06 11:55 ` vries at gcc dot gnu.org

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-30074-4717-4FeLjx54fE@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).