Date: Sat, 24 Apr 1999 00:10:17 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: Greg Lehey <grog@lemis.com> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: Problems with symbol sequences in recent kernels Message-ID: <37208D59.4A8670E8@newsguy.com> References: <19990423153323.P91260@freebie.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey wrote: > > This has worked quite nicely for some time. Since yesterday, after > building a kernel with newbus support, I get strange messages if I > read in the Vinum symbols before reading in the kernel symbols: ... > I debugged gdb and found that it was finding these references > (opt_global.h) in cd9660_rrip.o, which it read after reading the Vinum > kld symbols. If I can convince it to read the kernel symbols first, I > don't have any trouble. I don't think that it's anything to do with > that particular file; there must be about 30 files in a typical kernel > build which refer to this symbol. > > If I don't get any response on the list, I'll put in a PR, but I > thought there's a good chance that somebody will recognize this > problem and be able to fix it. Well, I don't recognize the problem, but I committed changes to cd9660_rrip.c after newbus got in. Could you try a kernel from before my changes got in? Just for the files I changed would be enough. This commit added Joliet Extensions support for cd9660, and affected cd9660 fs and mount_cd9660. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37208D59.4A8670E8>