On Wed, Feb 03, 2010 at 12:27:36AM +0100, Marc Bantle wrote:
> Package: schroot
> Version: 1.4.0-1
> Severity: normal
> 
> The command 'schroot -i -c A' crashes with segmentation fault,
> if there are files left from a previous session of
> configuration B in the /var/lib/schroot/session/ directory.
> 
> Console output:
> 
>   u...@host:~$ schroot -v -i -c A
>   Speicherzugriffsfehler                
> 
> No current schroot sessions are running.
> 
> Schroot works as expected as soon as /var/lib/schroot/session/
> is empty.

Could you possibly let me know what file was in
/var/lib/schroot/session/, and if you have it, the contents?

Can you reproduce the problem again?  If so, could you take me through
the steps to cause a file to be left in the session directory.  A
file in there on its own shouldn't cause problems, and certainly not
a segfaulty.  Additionally, could you run schroot with the additional
options '-v --debug=notice' which should help track down where the
fault is.

If you have time, you could also install schroot-dbg and run schroot
(as root) in gdb.  Just run 'gdb /usr/bin/schroot' and then
'run -i -c A' and when it segfaults, type 'backtrace' to get a
detailed trace of where the fault occured.



Thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Attachment: signature.asc
Description: Digital signature

Reply via email to