From: Daniel Jacobowitz <dan@debian.org>
To: Tachino Nobuhiro <tachino@jp.fujitsu.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Vamsi Krishna S." <vamsi_krishna@in.ibm.com>,
torvalds@transmeta.com, Jeff Jenkins <jefreyr@pacbell.net>,
linux-kernel@vger.kernel.org
Subject: Re: [bkpatch] Multiple threads in core dumps (was: Re: Thread
Date: Tue, 12 Mar 2002 11:42:52 -0500 [thread overview]
Message-ID: <20020312114252.A26117@nevyn.them.org> (raw)
In-Reply-To: <eliqqvfh.wl@nisaaru.dvs.cs.fujitsu.co.jp> <E16kkC8-0003QG-00@the-village.bc.nu> <it8211u5.wl@nisaaru.dvs.cs.fujitsu.co.jp>
In-Reply-To: <it8211u5.wl@nisaaru.dvs.cs.fujitsu.co.jp>
On Tue, Mar 12, 2002 at 08:07:30PM +0900, Tachino Nobuhiro wrote:
>
> Hello,
>
> At Tue, 12 Mar 2002 11:11:52 +0000 (GMT),
> Alan Cox wrote:
> >
> > > I am now trying to implement gcore system call on linux and have a
> > > great interest in your patch.
> >
> > The old Berkeley gcore wasnt a system call nor did it need to be. Ptrace
> > (and in their case grovelling around in /dev/mem) is more than sufficient
>
> IMHO, implementing gcore with ptrace has some problems, I think. If the process sleeps
> with TASK_UNINTERRUPTIBLE, almost ptrace() calls fails. If the process is already traced,
> you cannot use ptrace().
GDB implements gcore entirely via ptrace. Are there really so many
cases where that is inadequate? And the second objection (and maybe
the first) may go away if/when David Howells' new debugging interface
is ready.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-12 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 16:17 Thread registers dumped to core-file Jeff Jenkins
2002-03-09 6:45 ` Vamsi Krishna S.
2002-03-09 21:13 ` [bkpatch] Multiple threads in core dumps (was: Re: Thread registers dumped to core-file) Daniel Jacobowitz
2002-03-12 4:09 ` Tachino Nobuhiro
2002-03-12 11:11 ` [bkpatch] Multiple threads in core dumps (was: Re: Thread Alan Cox
2002-03-12 11:07 ` Tachino Nobuhiro
2002-03-12 16:42 ` Daniel Jacobowitz [this message]
2002-03-15 12:07 ` Thread registers dumped to core-file Vamsi Krishna S .
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=20020312114252.A26117@nevyn.them.org \
--to=dan@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jefreyr@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tachino@jp.fujitsu.com \
--cc=torvalds@transmeta.com \
--cc=vamsi_krishna@in.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