Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>,
	Marc Khouzam <marc.khouzam@ericsson.com>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [MI][patch v2] -break-list to specify "thread-group"
Date: Fri, 07 Dec 2012 15:44:00 -0000	[thread overview]
Message-ID: <50C20EE6.2030103@redhat.com> (raw)
In-Reply-To: <50C20D19.1070704@redhat.com>

On 12/07/2012 03:36 PM, Pedro Alves wrote:
> On 09/22/2012 01:58 PM, Yao Qi wrote:
>> On 09/21/2012 10:46 PM, Marc Khouzam wrote:
>>> or (if the bp applies to multiple inferiors, which I didn't quite
>>> out how to officially trigger, so I hacked the code to make sure
>>> the output was done properly in that case):
>>>
>>
>> I don't know ether.  I can't think of a case that multiple inferiors share a single pspace.
> 
> See the intro comment to program spaces in progspace.h.  It gives some examples, such
> as after a vfork (and before exit/exec), or some targets that work
> that way, like Ericsson's DICOS.
> 

Mandatory screenshot:

>./gdb ./testsuite/gdb.base/foll-vfork
(gdb) set detach-on-fork off
(gdb) set follow-fork-mode child
(gdb) start
Temporary breakpoint 1 at 0x4006f4: file ../../../src/gdb/testsuite/gdb.base/foll-vfork.c, line 29.
Starting program: /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.base/foll-vfork
Temporary breakpoint 1, main () at ../../../src/gdb/testsuite/gdb.base/foll-vfork.c:29
29        pid = vfork ();
(gdb) n
[New process 9882]
[Switching to process 9882]
30        if (pid == 0) {
(gdb) info inferiors
  Num  Description       Executable
* 2    process 9882      /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.base/foll-vfork
        is vfork child of inferior 1
  1    process 9878      /home/pedro/gdb/mygit/build/gdb/testsuite/gdb.base/foll-vfork
        is vfork parent of inferior 2
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) b main
Breakpoint 2 at 0x4006f4: file ../../../src/gdb/testsuite/gdb.base/foll-vfork.c, line 29.
(gdb) info breakpoints
Num     Type           Disp Enb Address            What
2       breakpoint     keep y   0x00000000004006f4 in main at ../../../src/gdb/testsuite/gdb.base/foll-vfork.c:29 inf 2, 1
(gdb)

-- 
Pedro Alves


  reply	other threads:[~2012-12-07 15:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 10:01 [MI][patch] " Marc Khouzam
2012-09-21 10:45 ` Marc Khouzam
2012-09-21 14:47   ` [MI][patch v2] " Marc Khouzam
2012-09-22 13:00     ` Yao Qi
2012-09-26 10:05       ` Marc Khouzam
2012-09-28 19:23         ` Tom Tromey
2012-10-01 16:10           ` Marc Khouzam
2012-10-01 16:17             ` Eli Zaretskii
2012-10-15 10:39             ` Marc Khouzam
2012-10-24 18:43               ` Marc Khouzam
2012-11-27 19:56                 ` Marc Khouzam
2012-11-28  6:07                   ` Abid, Hafiz
2012-11-30 18:35                     ` Tom Tromey
2012-09-28 19:21       ` Tom Tromey
2012-12-07 15:37       ` Pedro Alves
2012-12-07 15:44         ` Pedro Alves [this message]
2013-01-16 16:58           ` Marc Khouzam
2013-01-21 18:54             ` Pedro Alves
2013-01-22  0:09               ` Marc Khouzam
2012-09-28 19:10     ` Tom Tromey
2012-09-28 19:18     ` Tom Tromey
2012-09-21 18:12 ` [MI][patch] " André Pönitz
2012-09-21 18:54   ` Marc Khouzam

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=50C20EE6.2030103@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=yao@codesourcery.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