Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC v2] fix regressions with target-async
Date: Wed, 05 Mar 2014 20:38:00 -0000	[thread overview]
Message-ID: <53178B48.5060003@redhat.com> (raw)
In-Reply-To: <87txbc7b2s.fsf@fleche.redhat.com>

On 03/05/2014 06:30 PM, Tom Tromey wrote:
> Pedro> Confirmed, building with expat makes threaded debugging work:
> ...
> Pedro> (You can find an expat build at ~palves:/home/palves/opt/)
> 
> Thanks.  With this I was able to verify that your theory about the AIX
> to_attach method was correct -- I could make my patched gdb crash by
> debugging a multi-threaded inferior and then "attach"ing to a new
> process.

OK.

> The patch to aix-thread is pretty simple.  It regression tests
> reasonably well, but not perfectly... the test suite on AIX provokes a
> number of internal errors, and with my patch they can be reported
> against different tests.  I suspect this is timing sensitive though,
> perhaps latent races in the existing code, as the internal errors in
> question are all preceded by a failing call to
> aix-thread.c:ptrace_check.
> 
> For example:
> 
>     (gdb) next
>     thread_function (arg=0x0) at ../../../gdb/gdb/testsuite/gdb.threads/pending-step
>     .c:57
>     57              (*myp) ++; /* insert breakpoint here */
>     aix-thread: ptrace (50, 38011047) returned -1 (errno = 22 Invalid argument)
>     (gdb) next
>     ../../gdb/gdb/breakpoint.c:15064: internal-error: insert_single_step_breakpoint:
>      Assertion `single_step_breakpoints[1] == NULL' failed.
> 
> I wonder whether this is good enough.

Yes, I can't imagine this being related.

-- 
Pedro Alves


  reply	other threads:[~2014-03-05 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 17:48 Tom Tromey
2014-02-28 18:18 ` Pedro Alves
2014-02-28 18:26   ` Tom Tromey
2014-02-28 18:51     ` Pedro Alves
2014-02-28 18:54       ` Joel Brobecker
2014-02-28 19:19     ` Tom Tromey
2014-03-03 16:24   ` Tom Tromey
2014-03-03 16:38     ` Pedro Alves
2014-03-04 14:25       ` Tom Tromey
2014-03-04 15:10         ` Tom Tromey
2014-03-04 15:29           ` Joel Brobecker
2014-03-04 15:33             ` Tom Tromey
2014-03-04 21:25         ` Pedro Alves
2014-03-05  0:13           ` Tom Tromey
2014-03-05  0:14           ` Pedro Alves
2014-03-05 18:56             ` Tom Tromey
2014-03-05 20:38               ` Pedro Alves [this message]
2014-03-05 21:33                 ` Tom Tromey
2014-03-06 15:46                   ` Tom Tromey

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=53178B48.5060003@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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