Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	saugustine@google.com
Subject: Re: Fun with LD_PRELOAD
Date: Thu, 06 Feb 2014 07:58:00 -0000	[thread overview]
Message-ID: <m338jwad1h.fsf@sspiff.org> (raw)
In-Reply-To: <52F28CF7.8040206@redhat.com> (Pedro Alves's message of "Wed, 05	Feb 2014 19:11:51 +0000")

Pedro Alves <palves@redhat.com> writes:
> (removed guile)
>
> As we're talking about it,
>
> On 02/05/2014 06:21 PM, Doug Evans wrote:
>
>> For example, a colleague at Google tripped over a bug that requires a
>> specific timing to replicate.  I don't have all the details at hand,
>> but I think I'm hitting the same assert.
>> 
>> infrun.c:1948: internal-error: resume: Assertion
>> `pc_in_thread_step_range (pc, tp)' failed.
>> 
>> AIUI, It happens, for example, when the user does a "next", and a
>> signal arrives on another thread while the thread being next'd has
>> stepped into a subroutine (thus requiring gdb to step out to implement
>> the semantics of "next").  I now have a simple repro (at least for the
>> assert I'm seeing), and it was very straightforward to write.  It
>> involves tracking the PTRACE_SINGLESTEP being issued to one thread
>> (that implement "next") and at the right time send a signal to another
>> thread.
>
> perhaps you could check whether the patch at
>
>   https://sourceware.org/ml/gdb-patches/2014-01/msg00910.html
>
> also fixes your reproducer?

Yes it does, thanks.


      reply	other threads:[~2014-02-06  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02 22:08 Doug Evans
2014-02-04 11:21 ` Ludovic Courtès
2014-02-05 18:21   ` Doug Evans
2014-02-05 19:11     ` Pedro Alves
2014-02-06  7:58       ` Doug Evans [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=m338jwad1h.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ludo@gnu.org \
    --cc=palves@redhat.com \
    --cc=saugustine@google.com \
    /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