Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA/gdbserver: GDB internal-error debugging threaded program with breakpoint and forks
Date: Fri, 24 Jun 2016 21:57:00 -0000	[thread overview]
Message-ID: <31daa4d2-359d-db9a-e9c8-d7bfbb327570@redhat.com> (raw)
In-Reply-To: <20160624181152.GD3295@adacore.com>

I haven't gone through this with fine-tooth comb yet, but,
will we still have the same problem if _two_ threads (or inferiors...)
fork at the "same" time, and we end up reporting one fork, while
leaving the another one pending?

Thanks,
Pedro Alves


  reply	other threads:[~2016-06-24 21:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 17:16 RFH: failed assert debugging threaded+fork program over gdbserver Joel Brobecker
2016-05-12 17:42 ` Don Breazeal
2016-06-23 22:59   ` Joel Brobecker
2016-06-24 18:12     ` RFA/gdbserver: GDB internal-error debugging threaded program with breakpoint and forks (was: "Re: RFH: failed assert debugging threaded+fork program over gdbserver") Joel Brobecker
2016-06-24 21:57       ` Pedro Alves [this message]
2016-06-24 22:36         ` RFA/gdbserver: GDB internal-error debugging threaded program with breakpoint and forks Joel Brobecker
2016-06-24 22:37           ` Pedro Alves
2016-06-27 22:32             ` Joel Brobecker
2016-06-28 19:40               ` Pedro Alves
2016-07-05 16:49                 ` Joel Brobecker
2016-06-24 21:52     ` RFH: failed assert debugging threaded+fork program over gdbserver Breazeal, Don

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=31daa4d2-359d-db9a-e9c8-d7bfbb327570@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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