From owner-freebsd-current Fri Apr 23 8:15:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 511971548E for ; Fri, 23 Apr 1999 08:15:13 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA19096; Sat, 24 Apr 1999 00:12:19 +0900 (JST) Message-ID: <37208D59.4A8670E8@newsguy.com> Date: Sat, 24 Apr 1999 00:10:17 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Greg Lehey Cc: FreeBSD current users Subject: Re: Problems with symbol sequences in recent kernels References: <19990423153323.P91260@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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