Bug 25361

Addenda: this apparently only occurs on alpha.

Both the -stable and -current with kernels and userland later than February 26
do not show this problem.

A -current with a userland of 2/13 and a kernel from yesterday shows this
problem. 

I believe the problem has been addressed, but I'll reconfirm tonite after a
buildworld.

-matt



> 
> >Number:         25361
> >Category:       bin
> >Synopsis:       dump(8) command segfaults
> >Confidential:   no
> >Severity:       serious
> >Priority:       medium
> >Responsible:    freebsd-bugs
> >State:          open
> >Quarter:        
> >Keywords:       
> >Date-Required:
> >Class:          sw-bug
> >Submitter-Id:   current-users
> >Arrival-Date:   Sun Feb 25 12:40:00 PST 2001
> >Closed-Date:
> >Last-Modified:
> >Originator:     Christian Weisgerber
> >Release:        FreeBSD 5.0-CURRENT alpha
> >Organization:
> >Environment:
> System: FreeBSD kemoauc.mips.inka.de 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Sat Feb 24 14:37:31 CET 2001 naddy@kemoauc.mips.inka.de:/usr/src/sys/compile/KEMOAUC alpha
> 
> >Description:
> 
> The dump(8) command segfaults:
> 
> $ dump 0af /dev/null /
>   DUMP: Date of this level 0 dump: Sun Feb 25 20:44:21 2001
>   DUMP: Date of last level 0 dump: the epoch
>   DUMP: Dumping /dev/da0a (/) to /dev/null
>   DUMP: mapping (Pass I) [regular files]
>   DUMP: mapping (Pass II) [directories]
>   DUMP: estimated 67655 tape blocks.
>   DUMP: dumping (Pass III) [directories]
>   DUMP: dumping (Pass IV) [regular files]
>   DUMP: SIGSEGV: ABORTING!
>   DUMP: SIGSEGV: ABORTING!
>   DUMP: SIGSEGV: ABORTING!
>   DUMP: SIGSEGV: ABORTING!
>   DUMP: SIGSEGV: ABORTING!
> Segmentation fault (core dumped)
> 
> dump was working fine in -current as of Dec 25.  The only changes
> to it since then are the introduction of <sys/queue.h> instead of
> a home-rolled list and the replacement of '\007' with '\a'.  These
> changes are innocuous; if backed out, dump still segfaults.  This
> suggests that the problem has been triggered by a kernel change.
> 
> >How-To-Repeat:
> 
> $ dump 0af /dev/null /
> 
> >Fix:
> 
> None known.
> 
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-bugs" in the body of the message
>

Matthew Jacob:
> 
> Both the -stable and -current with kernels and userland later than February 26
> do not show this problem.

Sorry, but I'm running kernel and userland from March 4, and this
is *not* resolved.

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de

-current or -stable?


On Tue, 6 Mar 2001, Christian Weisgerber wrote:

> Matthew Jacob:
> > 
> > Both the -stable and -current with kernels and userland later than February 26
> > do not show this problem.
> 
> Sorry, but I'm running kernel and userland from March 4, and this
> is *not* resolved.
> 
> -- 
> Christian "naddy" Weisgerber                          naddy@mips.inka.de
>

Matthew Jacob:

> > Sorry, but I'm running kernel and userland from March 4, and this
> > is *not* resolved.
> 
> -current or -stable?

-CURRENT.

-- 
Christian "naddy" Weisgerber                          naddy@mips.inka.de

Comment 6 Matt Jacob 2001-03-28 17:20:53 UTC

State Changed
From-To: open->closed

John Baldwin fixed the kernel problems that caused this.