[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#189058: base-installer segfaults during install

On Tue, Apr 15, 2003 at 11:23:48PM -0400, Joe Nahmias wrote:
> Hash: SHA1
> Chris Tillman wrote:
> > On Mon, Apr 14, 2003 at 09:49:13PM -0400, Joe Nahmias wrote:
> > I believe debootstrap uses wget to download. Can you wget files
> > manually? Trying to pin down whether wget is segfaulting or 
> > debootstrap. You might be able to add options to wget to make it 
> > verbose. You can add --verbose to the debootstrap call.
> Hello Chris,
> I modified /var/lib/dpkg/info/base-installer.postinst as follows:
> a) I added a set -x at the top of the script.
> b) I added the --verbose option to the debootstrap line.
> With this done, I tried rerunning the base install step.  The script
> kicks off debootstrap with the following command line:
> `debootstrap --components=main --boot-floppies --verbose sarge /target http://ftp.us.debian.org/debian/`
> This is produces the following output:
> ==========8<=====================
> P: 0 100 Downloading Release file
> I: Validating /target/debootstrap.invalid_dists_sarge_Release
> P: 100 100 Downlaoding Release file
> P: 0 8040974 Downloading Packages files
> I: Retrieving http://ftp.us.debian.org/debian/dists/sarge/main/binary-i386/Packages.gz
> Segmentation fault
> base-installer's postinst exited with status 35584
> installer[44]: Configuring 'base-installer' failed with error code 256
> installer[44]: Menu item 'base-installer' failed.
> ==========>8=====================
> So it would seem that debootstrap is at fault...
> Also, poking around, I noticed that debootstrap writes an error log
> file into /target/var/log/debootstrap.err.log.  This file contains:
> ==========8<=====================
> id: unknown user name: 0
> [: 0: unknown operand
> printf: No such file or directory
> printf: No such file or directory
> ==========>8=====================
> I guess this means that `id` in busybox-cvs is broken.  You can
> reproduce this by running `id` from the shell on vc2.  Should I file a
> bug??

Definitely, I think you found it.
> After this, I added a "set -x" to /usr/sbin/debootstrap and reran the
> base-installer.  Boy, did I get alot of output!!  Anyways, it seems that
> the segfault happens in a call to just_get() which is defined in
> /usr/lib/debootstrap/functions.  It is called as:
> `just_get http://ftp.us.debian.org/debian/dists/sarge/main/binary-i386/Packages.gz /target/debootstrap.invalid_dists_sarge_main_binary-i386_Packages.gz`
> After setting the "from" and "dest" variables, it does a `mkdir -p
> /target` and then does the tests on lines 169 and 171 and then
> segfaults _before_ calling wgetprogress (apparently, since it doesn't
> print the call to it).

Anthony will appreciate your summarization in a debootstrap bug.
Sounds like you've got it nailed down to the line number.


Chris Tillman
- Linux Rox -

Reply to: