Re: ptracing a task from core_pattern pipe

2013-03-27 Thread Denys Vlasenko
On 03/27/2013 04:26 AM, Daniel Walker wrote: > On Mon, Mar 25, 2013 at 10:48:07AM +0100, Denys Vlasenko wrote: >> On 03/19/2013 09:19 PM, Oleg Nesterov wrote: The above is regarding the situation which I'm running my corepipe_app , i.e. my system doesn't have a disk to save a core file fo

Re: ptracing a task from core_pattern pipe

2013-03-26 Thread Daniel Walker
On Mon, Mar 25, 2013 at 10:48:07AM +0100, Denys Vlasenko wrote: > On 03/19/2013 09:19 PM, Oleg Nesterov wrote: > >> The above is regarding the situation which I'm running my corepipe_app , > >> i.e. my system doesn't have a disk to save a core file for parsing. > > > > Can't you process the data i

Re: ptracing a task from core_pattern pipe

2013-03-25 Thread Denys Vlasenko
On 03/19/2013 09:19 PM, Oleg Nesterov wrote: >> The above is regarding the situation which I'm running my corepipe_app , >> i.e. my system doesn't have a disk to save a core file for parsing. > > Can't you process the data inplace? You do not need to save it to disk. Daniel said: >> I'm trying t

Re: ptracing a task from core_pattern pipe

2013-03-19 Thread Oleg Nesterov
On 03/18, Daniel Walker wrote: > > On Mon, Mar 18, 2013 at 06:03:02PM +0100, Oleg Nesterov wrote: > > > > > For instance, I ptrace attach from inside the corepipe_app then try > > > PTRACE_GETREGS and you get -ESRCH . > > > > Sure. PTRACE_GETREGS and (almost) any other request can only succeed > >

Re: ptracing a task from core_pattern pipe

2013-03-18 Thread Daniel Walker
On Mon, Mar 18, 2013 at 06:03:02PM +0100, Oleg Nesterov wrote: > > Assume that's not happening, why would ptrace give me -ESRCH, yet > > /proc//status would show me ptrace attached to the thread. > > And why do you think this should be explained by SIGKILL? It's an assumption, if I knew before yo

Re: ptracing a task from core_pattern pipe

2013-03-18 Thread Oleg Nesterov
On 03/17, Daniel Walker wrote: > > On Sun, Mar 17, 2013 at 03:34:46PM +0100, Oleg Nesterov wrote: > > > > It sleeps only after it dumps the core. It only sleeps to ensure we > > do not close the write side prematurely. > > The dumper thread is sleeping when the corepipe_app runs .. I ran "cat > /pr

Re: ptracing a task from core_pattern pipe

2013-03-17 Thread Daniel Walker
On Sun, Mar 17, 2013 at 03:34:46PM +0100, Oleg Nesterov wrote: > > > (Just in case, this was recently changed. After > > > coredump-ensure-that-sigkill-always-kills-the-dumping-thread.patch in -mm > > > tree the dumper doesn't run in SIGNAL_GROUP_EXIT, but probably this > > > doesn't matter) > >

Re: ptracing a task from core_pattern pipe

2013-03-17 Thread Oleg Nesterov
On 03/16, Daniel Walker wrote: > > On Sat, Mar 16, 2013 at 06:58:45PM +0100, Oleg Nesterov wrote: > > On 03/15, Daniel Walker wrote: > > > > > > I was writing an application to ptrace a process which is dumping core > > > from inside the pipe application for core_pattern. > > > > This was never pos

Re: ptracing a task from core_pattern pipe

2013-03-16 Thread Daniel Walker
On Sat, Mar 16, 2013 at 06:58:45PM +0100, Oleg Nesterov wrote: > On 03/15, Daniel Walker wrote: > > > > I was writing an application to ptrace a process which is dumping core > > from inside the pipe application for core_pattern. > > This was never possible. And never will, I think. > > > So for

Re: ptracing a task from core_pattern pipe

2013-03-16 Thread Oleg Nesterov
Hi Daniel, Sorry, I can't understand your email... On 03/15, Daniel Walker wrote: > > I was writing an application to ptrace a process which is dumping core > from inside the pipe application for core_pattern. This was never possible. And never will, I think. > So for example you make core patt

ptracing a task from core_pattern pipe

2013-03-15 Thread Daniel Walker
Hi, I was writing an application to ptrace a process which is dumping core from inside the pipe application for core_pattern. So for example you make core pattern equal to something like "|/bin/corepipe_app" then the kernel runs that app prior to actually killing the process that failed. Before