, Stéphane Graber wrote:
On 04/24/2013 02:10 PM, Hans Feldt wrote:
-Original Message-
From: Serge Hallyn [mailto:serge.hal...@ubuntu.com]
Sent: den 23 april 2013 14:52
To: Hans Feldt
Cc: lxc-users@lists.sourceforge.net
Subject: Re: [Lxc-users] Problem with core dumps generated from
containers
Graber wrote:
On 04/24/2013 02:10 PM, Hans Feldt wrote:
-Original Message-
From: Serge Hallyn [mailto:serge.hal...@ubuntu.com]
Sent: den 23 april 2013 14:52
To: Hans Feldt
Cc: lxc-users@lists.sourceforge.net
Subject: Re: [Lxc-users] Problem with core dumps generated from
containers
Quoting Stéphane Graber (stgra...@ubuntu.com):
On 04/25/2013 02:18 PM, Hans Feldt wrote:
Thanks great! But what I don't (yet) understand is shouldn't the new %P
behaviour be the default of %p instead?
I mean a container PID never makes sense in host user space since there
is a 1:n
-Original Message-
From: Serge Hallyn [mailto:serge.hal...@ubuntu.com]
Sent: den 23 april 2013 14:52
To: Hans Feldt
Cc: lxc-users@lists.sourceforge.net
Subject: Re: [Lxc-users] Problem with core dumps generated from
containers, apport
260 is the PID of my test program (sleep 1000
My guess would be similar to this but slightly different. I'd guess
that apport on the host sees the SEGV in kernel log. That will have
the correct pid for the kernel to look up the task, however it will
crosscheck /proc/$$/maps and such against userspace on the host,
which will cause debug info
