From: Tachino Nobuhiro <tachino@jp.fujitsu.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: tachino@jp.fujitsu.com (Tachino Nobuhiro),
dan@debian.org (Daniel Jacobowitz),
vamsi_krishna@in.ibm.com (Vamsi Krishna S.),
torvalds@transmeta.com, jefreyr@pacbell.net (Jeff Jenkins),
linux-kernel@vger.kernel.org
Subject: Re: [bkpatch] Multiple threads in core dumps (was: Re: Thread
Date: Tue, 12 Mar 2002 20:07:30 +0900 [thread overview]
Message-ID: <it8211u5.wl@nisaaru.dvs.cs.fujitsu.co.jp> (raw)
In-Reply-To: <E16kkC8-0003QG-00@the-village.bc.nu>
In-Reply-To: <eliqqvfh.wl@nisaaru.dvs.cs.fujitsu.co.jp> <E16kkC8-0003QG-00@the-village.bc.nu>
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().
next prev parent reply other threads:[~2002-03-12 11:08 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:07 ` Tachino Nobuhiro [this message]
2002-03-12 16:42 ` [bkpatch] Multiple threads in core dumps (was: Re: Thread Daniel Jacobowitz
2002-03-12 11:11 ` Alan Cox
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=it8211u5.wl@nisaaru.dvs.cs.fujitsu.co.jp \
--to=tachino@jp.fujitsu.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dan@debian.org \
--cc=jefreyr@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®