Date: Sat, 25 Jul 1998 14:10:01 -0700 (PDT) From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) To: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/7393: du throws SIGSEGV whenever '-c' option is used (at du.c:226) Message-ID: <199807252110.OAA10488@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/7393; it has been noted by GNATS.
From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= )
To: jhicks@glenatl.glenayre.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/7393: du throws SIGSEGV whenever '-c' option is used (at du.c:226)
Date: 25 Jul 1998 23:02:17 +0200
jhicks@glenatl.glenayre.com writes:
> du throws SIGSEGV whenever '-c' option is used (at du.c:226)
>
> du.c:224
> if (cflag) {
> p = savedp->fts_parent;
> (void) printf("%ld\ttotal\n", howmany(p->fts_number, blocksize));
> }
>
>
> (gdb) display *savedp
> 3: *savedp = {
> fts_cycle = 0xd0d0d0d0,
> fts_parent = 0xd0d0d0d0,
> fts_link = 0xd0d0d0d0,
> [...]
This FTSENT is quite obviously totally fubar. Could you please provide
some more information about the exact circumstances in which the bug
manifested itself? I haven't succeeded in reproducing it on my
machine. Do you still have (or could you produce) a core dump? If so,
could you tar together the core dump, your (unstripped) du binary, and
a description of the circumstances of the SIGSEGV, and put the tarball
up somewhere where I can get it?
DES
--
Dag-Erling Smørgrav - dag-erli@ifi.uio.no
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807252110.OAA10488>