Andrew Morton <[EMAIL PROTECTED]> wrote:
> Yes, I agree - I don't think we presently have a way of avoiding having
> to send all of that uninteresting data down the pipe.
Have the kernel fork and exec a debug program "just in time" with the dying
process ptrace-attached in advance. That program
On Fri, 30 Mar 2007 19:29:23 +0900 "Kawai, Hidehiro" <[EMAIL PROTECTED]> wrote:
> > core_pattern:
> > ...
> > . If the first character of the pattern is a '|', the kernel will treat
> > the rest of the pattern as a command to run. The core dump will be
> > written to the standard input of t
Hi,
Andrew Morton wrote:
> On Thu, 29 Mar 2007 20:16:59 +0100
> David Howells <[EMAIL PROTECTED]> wrote:
>
>>Pavel Machek <[EMAIL PROTECTED]> wrote:
>>
Userland core dumper is useful because it is relatively easy to be
customized, but its reliability highly depends on the application
>>>
On Thu, 29 Mar 2007 20:16:59 +0100
David Howells <[EMAIL PROTECTED]> wrote:
> Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> > > Userland core dumper is useful because it is relatively easy to be
> > > customized, but its reliability highly depends on the application
> > > programs.
> >
> > Fix use
Pavel Machek <[EMAIL PROTECTED]> wrote:
> > Userland core dumper is useful because it is relatively easy to be
> > customized, but its reliability highly depends on the application
> > programs.
>
> Fix userland core dumper to be reliable, then.
I don't think it's that easy. The userland core d
Hi!
> I have discussed with my colleagues why you say "ugly" against my
> procfs interface, then I noticed I may have misunderstood what you said.
> Is the reason for saying "ugly" two interfaces, i.e. preexisting ulimit
> (get/setrlimit) and my proc entry, exist to control core file size?
Yes.
Hi Pavel,
Thank you for your reply.
I'm sorry for my late reply.
I have discussed with my colleagues why you say "ugly" against my
procfs interface, then I noticed I may have misunderstood what you said.
Is the reason for saying "ugly" two interfaces, i.e. preexisting ulimit
(get/setrlimit) and m
Hi!
> This patch adds an interface to set/reset a flag which determines
> anonymous shared memory segments should be dumped or not when a core
> file is generated.
>
> /proc//coredump_omit_anonymous_shared file is provided to access
> the flag. You can change the flag status for a particular proc
This patch adds an interface to set/reset a flag which determines
anonymous shared memory segments should be dumped or not when a core
file is generated.
/proc//coredump_omit_anonymous_shared file is provided to access
the flag. You can change the flag status for a particular process by
writing to
This patch adds an interface to set/reset a flag which determines
anonymous shared memory segments should be dumped or not when a core
file is generated.
/proc//coredump_omit_anonymous_shared file is provided to access
the flag. You can change the flag status for a particular process by
writing to
10 matches
Mail list logo