public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30935] Regression exposed by new gdb.python/py-progspace-events.exp  test and native-extended-gdbserver board
Date: Tue, 03 Oct 2023 13:56:59 +0000	[thread overview]
Message-ID: <bug-30935-4717-RJAl3EPWl5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30935-4717@http.sourceware.org/bugzilla/>

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl dot ca

--- Comment #2 from Simon Marchi <simon.marchi at polymtl dot ca> ---
Thanks, I reproduced it and made a minimal one-liner:

  ./gdb -batch -nx -q --data-directory=data-directory -ex "tar ext |
../gdbserver/gdbserver --once - a.out" -ex "set detach-on-fork off" -ex "tb
parent" -ex c -ex "inferior 2" -ex c -ex "inferior 1" -ex step

using the following program:

```
#include <unistd.h>

void parent () {}
void child () {}

int main()
{
  if (fork ()) {
      parent();
  } else {
      child();
  }
}
```

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

  parent reply	other threads:[~2023-10-03 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 21:15 [Bug gdb/30935] New: " aburgess at redhat dot com
2023-10-02 21:15 ` [Bug gdb/30935] " aburgess at redhat dot com
2023-10-02 22:58 ` aburgess at redhat dot com
2023-10-03 13:56 ` simon.marchi at polymtl dot ca [this message]
2023-10-03 14:25 ` simon.marchi at polymtl dot ca
2023-10-03 16:23 ` aburgess at redhat dot com
2023-10-05 17:23 ` cvs-commit at gcc dot gnu.org
2023-10-05 17:24 ` simon.marchi at polymtl dot ca

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-30935-4717-RJAl3EPWl5@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).