[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53B553A4.6070407@in.ibm.com>
Date: Thu, 03 Jul 2014 18:29:16 +0530
From: "Suzuki K. Poulose" <suzuki@...ibm.com>
To: Phillip Susi <psusi@...ntu.com>,
Janani Venkataraman <jananive@...ux.vnet.ibm.com>,
Karel Zak <kzak@...hat.com>
CC: amwang@...hat.com, rdunlap@...otime.net, andi@...stfloor.org,
aravinda@...ux.vnet.ibm.com, hch@....de, mhiramat@...hat.com,
jeremy.fitzhardinge@...rix.com, xemul@...allels.com,
suzuki@...ux.vnet.ibm.com, kosaki.motohiro@...fujitsu.com,
adobriyan@...il.com, tarundsk@...ux.vnet.ibm.com,
vapier@...too.org, roland@...k.frob.com, tj@...nel.org,
ananth@...ux.vnet.ibm.com, gorcunov@...nvz.org, avagin@...nvz.org,
oleg@...hat.com, eparis@...hat.com, d.hatayama@...fujitsu.com,
james.hogan@...tec.com, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, coreutils@....org,
procps@...elists.org, util-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/33] [RFC] Non disruptive application core dump infrastructure
On 03/24/2014 07:24 PM, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 3/24/2014 5:43 AM, Janani Venkataraman wrote:
>> Gcore attaches to the process using gdb and runs the gdb gcore
>> command and then detaches. In gcore the dump cannot be issued from
>> a signal handler context as fork() is not signal safe and moreover
>> it is disruptive in
>
> You can fork+exec from a signal handler just fine.
Please go through the bug, and especially the comment below :
https://sourceware.org/bugzilla/show_bug.cgi?id=4737#c12
Cheers
Suzuki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists