Date: Tue, 06 Mar 2001 19:28:32 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: naddy@mips.inka.de (Christian Weisgerber), freebsd-alpha@FreeBSD.ORG Subject: Re: Dump segv w/devfs (was Re: My list of -CURRENT problems) Message-ID: <10098.983903312@critter> In-Reply-To: Your message of "Tue, 06 Mar 2001 13:25:12 EST." <15013.11144.757425.205222@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <15013.11144.757425.205222@grasshopper.cs.duke.edu>, Andrew Gallatin writes: > >Christian Weisgerber writes: > > Andrew Gallatin <gallatin@cs.duke.edu> wrote: > > > > > Perhaps it is scsi-controller specific? What type of scsi controller > > > is in this machine? > > > > sym(4), although I can't imagine this making a difference. ><...> > >OK, it seems to be related to devfs. Dumping with /dev/null as a file >crashes. Dumping to a normal file elsewhere works. Dumping through a >redirect to /dev/null (tcsh) seems to work as well. > >/dev/null as a "file" works just fine w/o devfs. > >Eg: > >dump 0af - / > /dev/null - works >dump 0af /usr/tmp/foo / - works >dump 0af /dev/null / - SEGV w/devfs, works with normal /dev How about running dump under a debugger and try to find out where it SEGV's ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10098.983903312>