util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <suzuki@in.ibm.com>
To: Ondrej Oprala <ooprala@redhat.com>,
	Janani Venkataraman <jananive@linux.vnet.ibm.com>,
	util-linux@vger.kernel.org
Cc: ananth@linux.vnet.ibm.com, Tarundeep Singh <tarundsk@linux.vnet.ibm.com>
Subject: Re: Non disruptive application core dump infrastructure
Date: Thu, 29 May 2014 18:15:37 +0530	[thread overview]
Message-ID: <53872BF1.5030303@in.ibm.com> (raw)
In-Reply-To: <53871E15.1040209@redhat.com>

On 05/29/2014 05:16 PM, Ondrej Oprala wrote:
> On 05/29/2014 01:44 PM, Janani Venkataraman wrote:
>> Hi,
>>
>> We have developed a tool called "gencore" which captures the core of
>> an application without
>> disrupting its process. The dump is collected non-disruptively and
>> this tool currently supports
>> s390, x86 and power systems.
>>
>> THE TOOL:
>>
>> The tool can perform non-disruptive third party dumps. The tool also
>> contains a library "libgencore"
>> which helps applicationsto trigger self dumps.
>>
>> The tool can perform:
>>
>> 1) Third party dump: The pid of the process to dumped is given along
>> with name of the core-file to
>> be created.
>>
>> eg.
>>
>> [janani@localhost]:gencore 6616 core.test
>>
>> 2) Self dump: The programs can request a self-dump using gencore()
>> API, provided throughlibgencore. This
>> is implemented through a daemon which listens on a UNIX Filesocket for
>> such requests. The daemon is started
>> immediately post installation. The program which requires the dump
>> makes use of the gencore() API and provides
>> the name of the core-file as a parameter.
>>
>> eg.
>>
>> /* Opening the library, in this case the library is present in the
>> /usr/lib64 */
>> lib = dlopen("libgencore.so", RTLD_LAZY);
>>
>> gencore = dlsym(lib, "gencore");
>>
>> Call the API:
>> gencore("/home/janani/core_test").
>>
>> BASIC IDEA:
>>
>> The basic idea is that the threads of the process are held using
>> ptrace calls and the dump is generated in the
>> ELF format using the /proc/pid filesystem.
>>
>> PATCH SET:
>> We have designed this tool based on the discussions with linux kernel
>> community. The patches have been posted
>> at: https://lkml.org/lkml/2014/3/20/138
>>
>> Do you think this can be part of the util-linux bundle? We can tweak
>> it to make it work as a package in util-linux.
>>
>> Let us know your reviews and comments.
>>
>> Thanks.
>> Janani
>>
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe util-linux" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Interesting,
> but how is this different from attaching to a process with GDB and using
> the gcore command? Or to automate it more, using the gcore script that
> comes with GDB?
> Cheers,
> Ondrej
> 

There are two major issues with that.

1) GDB uses PTRACE_ATTACH and hence the process gets a SIGSTOP.

2) A process cannot initiate the request to dump itself, say from a
signal handler. (since fork() is not signal safe)

Thanks
Suzuki


  reply	other threads:[~2014-05-29 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 11:44 Non disruptive application core dump infrastructure Janani Venkataraman
2014-05-29 11:46 ` Ondrej Oprala
2014-05-29 12:45   ` Suzuki K. Poulose [this message]
2014-05-29 13:17     ` Ondrej Oprala
2014-05-29 18:23       ` Suzuki K. Poulose
2014-07-03 10:30         ` Suzuki K. Poulose
2014-07-03 12:36           ` Ondrej Oprala
2014-07-03 12:58             ` Suzuki K. Poulose
2014-07-04 11:56               ` Ondrej Oprala
2014-07-30 10:28                 ` Suzuki K. Poulose

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=53872BF1.5030303@in.ibm.com \
    --to=suzuki@in.ibm.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=jananive@linux.vnet.ibm.com \
    --cc=ooprala@redhat.com \
    --cc=tarundsk@linux.vnet.ibm.com \
    --cc=util-linux@vger.kernel.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 NNTP newsgroup(s).