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 threads/27812] [m32] linux-nat.c:1765: internal-error: virtual void linux_nat_target::resume(ptid_t, int, gdb_signal): Assertion `signo == GDB_SIGNAL_0' failed
Date: Sun, 09 May 2021 08:51:14 +0000	[thread overview]
Message-ID: <bug-27812-4717-XX4SrbOxvl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27812-4717@http.sourceware.org/bugzilla/>

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

--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
I tried to modify the example a bit, because sleep saves and restores errno, so
I was not sure how reliable the perror was.

So I've added:
...
#include <time.h>

static inline unsigned int
mysleep (unsigned int seconds)
{
  struct timespec ts = { 0, 0 };
  ts.tv_sec = (time_t) seconds;
  if (nanosleep (&ts, &ts) < 0)
    {
      perror ("mysleep");
      return ts.tv_sec;
    }
  return 0;
}

#define sleep(s) mysleep (s)
...

Interestingly, I still got:
...
mysleep: Invalid argument^M
...

More interestingly, I ran into:
...
/home/vries/gdb_versions/devel/src/gdb/linux-nat.c:1914: internal-error: wait
returned unexpected status 0x86^M
...

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

      parent reply	other threads:[~2021-05-09  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 12:46 [Bug threads/27812] New: " vries at gcc dot gnu.org
2021-05-03 12:50 ` [Bug threads/27812] " vries at gcc dot gnu.org
2021-05-03 12:51 ` vries at gcc dot gnu.org
2021-05-06 15:18 ` vries at gcc dot gnu.org
2021-05-06 15:26 ` simark at simark dot ca
2021-05-06 15:29 ` vries at gcc dot gnu.org
2021-05-06 15:41 ` simark at simark dot ca
2021-05-07 17:48 ` vries at gcc dot gnu.org
2021-05-08  4:18 ` vries at gcc dot gnu.org
2021-05-09  7:36 ` vries at gcc dot gnu.org
2021-05-09  8:51 ` vries at gcc dot gnu.org [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=bug-27812-4717-XX4SrbOxvl@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).