Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
	"Ulrich Weigand" <uweigand@de.ibm.com>,
	        Jan Kratochvil <jkratoch@redhat.com>
Subject: Re: Multi-exec patches
Date: Wed, 29 Jul 2009 22:03:00 -0000	[thread overview]
Message-ID: <m3vdlbtd1p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200907281301.34095.pedro@codesourcery.com> (Pedro Alves's message of "Tue\, 28 Jul 2009 13\:01\:33 +0100")

Tom> Can not resume the parent process over vfork in the foreground while 
Tom> holding the child stopped.  Try "set detach-on-fork" or "set schedule-multiple".
Tom> Recursive internal problem.
Tom> Aborted

Pedro> Can you get me a backtrace, to see what happened here?

For the record, I sent this in a separate note, the other day.

Tom> I also got this strange result:
Tom> (gdb) set detach-on-fork off
Tom> (gdb) set schedule-multiple on
Tom> (gdb) set non-stop on
Tom> (gdb) run
[...]
Pedro> This usually means that GDB tried to read registers from
Pedro> an LWP that wasn't stopped.  I'll try to catch this one.
Pedro> Are those commands above the whole set of commands?  I
Pedro> assume that you issued "set target-async on" and "set pagination off"
Pedro> somewhere too?

Nope!  So that is probably the problem.

Tom> Ok, this worked much better.  I was able to interrupt a cc1 process
Tom> during make!

Pedro> Cool!

I also tried setting a pending breakpoint on a function in cc1, then
running "make".  Nothing ever stopped at the breakpoint.  Is this
expected?

Tom> ../../archer/gdb/thread.c:708: internal-error: finish_thread_state: Assertion `tp' failed.

Pedro> If you have a chance to retry, could you please let me know if you
Pedro> can reproduce this one with patch 2/2 of the mini-series applied ?

I tried this and couldn't reproduce it.

Tom


  reply	other threads:[~2009-07-29 21:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 17:14 [rfc] Infrastructure to disable breakpoints during inferior startup Ulrich Weigand
2009-07-22 20:32 ` Tom Tromey
2009-07-23 15:49   ` Ulrich Weigand
2009-07-23 16:51     ` Tom Tromey
2009-07-23 18:06       ` Ulrich Weigand
2009-07-23 18:57         ` Pedro Alves
2009-07-24 22:49           ` Tom Tromey
2009-07-24 23:32             ` Multi-exec patches (Was: [rfc] Infrastructure to disable breakpoints during inferior startup) Tom Tromey
2009-07-25 16:05               ` Pedro Alves
2009-07-25 19:31                 ` Pedro Alves
2009-07-27 17:39                 ` Multi-exec patches Tom Tromey
2009-07-27 18:45                   ` Tom Tromey
2009-07-28 14:28                   ` Pedro Alves
2009-07-29 22:03                     ` Tom Tromey [this message]
2009-07-31 15:45           ` [rfc] Infrastructure to disable breakpoints during inferior startup Ulrich Weigand
2009-08-03  3:07             ` Thiago Jung Bauermann
2009-08-03 18:13               ` Eli Zaretskii
2009-08-05 18:14                 ` Ulrich Weigand
2009-08-05 18:58                   ` Eli Zaretskii
2009-08-06 17:46                   ` Tom Tromey
2009-08-06 18:42                     ` Eli Zaretskii
2009-08-06 19:12                       ` Michael Snyder

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=m3vdlbtd1p.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jkratoch@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=uweigand@de.ibm.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