[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/46148: cvs(1) broken in NetBSD 6.0_BETA
The following reply was made to PR bin/46148; it has been noted by GNATS.
From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
Subject: Re: bin/46148: cvs(1) broken in NetBSD 6.0_BETA
Date: Sat, 24 Mar 2012 15:24:14 -0400
On Sat, 24 Mar 2012 17:45:03 +0000 (UTC)
David Holland <dholland-bugs%netbsd.org@localhost> wrote:
> On Sat, Mar 24, 2012 at 04:45:02AM +0000, Matthew Mondor wrote:
> > I have no idea yet if this could be related, and if so, in which
> > situation this happens, but xcvs uses chdir(2) a lot, and I wonder if
> > the cwd is always consistent. It might be quick to assume a problem
> > with chdir/cwd, but I noticed that on netbsd-6 with ff8 (I never had
> > that problem with ff8 on netbsd-5), ff sometimes goes back to the
> > previous-previous directory that was used to save a file rather than
> > the previous one. And gtkfilechooser does use chdir. Of course, it
> > also could be a bug in ff8 or gtk2...
> I find this highly improbable -- the current directory is a vnode
> reference saved in the process structure. If it were changing behind
> the process's back to some other vnode because of e.g. a refcounting
> or locking issue, it's highly unlikely you'd see specifically the
> previous-previous directory; you'd get some arbitrary directory or
> strange behavior because a regular file got picked up instead.
> Likewise for the chdir call retrieving and setting the wrong vnode.
> (And if the pointer were getting arbitrarily corrupted, you'd be
> seeing crashes.)
You're probably right, yesterday I looked at the proc and lwp
structures and there's no reason to think that it could remember the
previous cwd (of course some shells can but that's irrelevant). It
could be that this ff8, spidermonkey or gtk2 bug only occurs on amd64,
too, as I only briefly ran netbsd-5 on amd64, mostly on i386, and I
didn't use netbsd-6 on i386 yet.
Main Index |
Thread Index |