public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "kevin.pouget at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13211] New: Async / Process group and interrupt not working
Date: Wed, 21 Sep 2011 11:36:00 -0000	[thread overview]
Message-ID: <bug-13211-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13211

             Bug #: 13211
           Summary: Async / Process group and interrupt not working
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: kevin.pouget@gmail.com
    Classification: Unclassified


The `interrupt` command seems not to be working correctly when pgid != pid

Testcase:
========
Execute the proc you want to debug from `make`
Check their pgid/pid: `ps -eo pid,pgid,args --sort pgid`
      PID  PGID COMMAND
    11555 11555 make run
    11556 11555 ./test

Start GDB with `target-async on` and attach to your process.
Continue it asynchronously `cont&`
Try to interrupt it `interrupt`
Nothing happens!


Reason:
======

in inf-ptrace.c:331, 
inf_ptrace_stop tries to kill `-inferior_process_group ()` which is 11556.

`perror` confirms that: "status: No such process"

(I'm not sure 1. why `inferior_process_group` returns the wrong pg, 2. why you
want to kill the entire group, my `make` did nothing wrong!)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-09-21 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 11:36 kevin.pouget at gmail dot com [this message]
2011-09-21 13:23 ` [Bug gdb/13211] " kevin.pouget at gmail dot com
2015-08-19 19:03 ` robertknight at gmail dot com
2022-04-22 12:38 ` tromey at sourceware dot org

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=bug-13211-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).