Re: current.freebsd.org snapshots and broken X11
Robert Watson wrote: > > Sounds good to me, as long as it runs :-). > > BTW, ran into another nit from the 02/13 snapshot. I installed the > X-kern-developer distribution, discovered X11 didn't work, so went back > into sysinstall to install X11 stuff. I selected some combination of X11 > components, and chose releng3.freebsd.org as the source -- sysinstall > coredumped. A second attempt at the same resulted in sysinstall hanging. > > This seems to be reproduceable -- what can I do to give you better > debugging information? cd /usr/src/release/sysinstall CC="gcc -g" make all ./sysinstall [list the exacts steps you took, so I can reproduce it too, or find that I can't :)] (core dump) gdb ./sysinstall sysinstall.core Usual procedure here (backtrace, etc). The problem will most likely be the member of a structure pointed by a NULL pointer being reference. Eg, mediaDevice->shutdown(...), i->kids. It would help further if you then break-pointed the function where the problem happened, and stepped through it to pinpoint when the variable turned to NULL (eg, mediaDevice->get(mediaDevice, ...)). -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
On Tue, 14 Mar 2000, Jordan K. Hubbard wrote: > I was actually talking about FreeBSD 4.0, not XFree86 4.0. :) D'oh! -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
I was actually talking about FreeBSD 4.0, not XFree86 4.0. :) > On Tue, 14 Mar 2000, Jordan K. Hubbard wrote: > > > I think I'm just going to go to the 3.4 bits; I don't have a definitive > > XFree86 distribution for 4.0 and I don't think I'm going to get one in > > time to make a difference. > > Not to mention that 4.0 has "issues" with some > hardware/software/etc. I can't get xfce to run in it, for example. > > Doug > -- > "Welcome to the desert of the real." > > - Laurence Fishburne as Morpheus, "The Matrix" > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
On Tue, 14 Mar 2000, Jordan K. Hubbard wrote: > I think I'm just going to go to the 3.4 bits; I don't have a definitive > XFree86 distribution for 4.0 and I don't think I'm going to get one in > time to make a difference. Not to mention that 4.0 has "issues" with some hardware/software/etc. I can't get xfce to run in it, for example. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
Sounds good to me, as long as it runs :-). BTW, ran into another nit from the 02/13 snapshot. I installed the X-kern-developer distribution, discovered X11 didn't work, so went back into sysinstall to install X11 stuff. I selected some combination of X11 components, and chose releng3.freebsd.org as the source -- sysinstall coredumped. A second attempt at the same resulted in sysinstall hanging. This seems to be reproduceable -- what can I do to give you better debugging information? On Tue, 14 Mar 2000, Jordan K. Hubbard wrote: > I think I'm just going to go to the 3.4 bits; I don't have a definitive > XFree86 distribution for 4.0 and I don't think I'm going to get one in > time to make a difference. > > - Jordan > > > > > It looks like the X11 associated with the snapshots on current.freebsd.org > > is still broken: > > > > /usr/libexec/ld-elf.so.1: Share object "libXThrStub.so.6" not found > > > > Installing -current boxes for testing and development would be a lot > > easier if this worked. :-) Especially leading up to releases when testing > > changes in the install is useful :-) > > > > Robert N M Watson > > > > [EMAIL PROTECTED] http://www.watson.org/~robert/ > > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > > TIS Labs at Network Associates, Safeport Network Services > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > Robert N M Watson [EMAIL PROTECTED] http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org snapshots and broken X11
I think I'm just going to go to the 3.4 bits; I don't have a definitive XFree86 distribution for 4.0 and I don't think I'm going to get one in time to make a difference. - Jordan > > It looks like the X11 associated with the snapshots on current.freebsd.org > is still broken: > > /usr/libexec/ld-elf.so.1: Share object "libXThrStub.so.6" not found > > Installing -current boxes for testing and development would be a lot > easier if this worked. :-) Especially leading up to releases when testing > changes in the install is useful :-) > > Robert N M Watson > > [EMAIL PROTECTED] http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message