Jacob Sherwood said on
[Sat, Jun 20, 2009 at 02:35:53PM -0400]:
> From: Jacob Sherwood
> Subject: Re: [Buildd-tools-devel] Bug#512350: Bug#512350: schroot Segfaults
> Okay, I think I figured out what happened that caused this problem
> because it's happening again. Here's
nlightenment I'll get the segfault.
Jacob
--
I am not a comedian; I am Lenny Bruce.
-- Lenny Bruce
Jacob Sherwood ja...@jacobsherwood.com
signature.asc
Description: Digital signature
ded to reinstall (because of my inability to reproduce it on a VM)
and amazingly enough, the issue went away.
I would say this is invalid now.
Thanks,
Jacob
--
I am not a comedian; I am Lenny Bruce.
-- Lenny Bruce
Jacob Sherwood ja...@jacobsherwood.com
signature.asc
Desc
On Tue, Jan 20, 2009 at 9:57 AM, Roger Leigh wrote:
> Could you possibly try running schroot in a debugger for me to
> pinpoint where this occurs? Also, the most likely cause (I think)
> would be something odd being set in the environment, since that's
> really the only think the shell can mess
Package: schroot
Version: 1.2.1-1
Severity: important
schroot segfaults whenever invoked from eesh:
[Mon 12:49][pts/5 0]$ eesh exec "schroot -p echo foo bar"
And in /var/log/syslog I see:
Jan 19 17:39:40 wolf kernel: [195438.971879] schroot[2338]: segfault at
0 ip 7fd0db117050 sp 7fffe4ab46c8 er
5 matches
Mail list logo
