Re: Core dumps on Current Make World this morning
do a 'make -k world' ... I had the same problem with vi, and the same
SegFault ... by using -k, it bypasses the error, which allows it to get to
the point that the newer vi is installed, which doesn't SegFault ...
On Tue, 2 Jan 2001, Charlie Root wrote:
All the machines that I have running Current dumped core at the same
place this morning.
=== share/termcap
ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder
/dev/null
Segmentation fault - core dumped
*** Error code 139
Stop in /usr/src/share/termcap.
*** Error code 1
For a couple of days now, I haven't been able to use vi because it also
dumps core on all the machines except the only one that was able to
build world and a new kernel yesterday, just good timing I guess. I
haven't seen this on the list.
Thanks,
ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
The Hermit Hacker wrote:
do a 'make -k world' ... I had the same problem with vi, and the same
SegFault ... by using -k, it bypasses the error, which allows it to get to
the point that the newer vi is installed, which doesn't SegFault ...
Thanks, I just started them all up with -k . I didn't even think of that.
Thanks again,
ed
On Tue, 2 Jan 2001, Charlie Root wrote:
All the machines that I have running Current dumped core at the same
place this morning.
=== share/termcap
ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder
/dev/null
Segmentation fault - core dumped
*** Error code 139
Stop in /usr/src/share/termcap.
*** Error code 1
For a couple of days now, I haven't been able to use vi because it also
dumps core on all the machines except the only one that was able to
build world and a new kernel yesterday, just good timing I guess. I
haven't seen this on the list.
Thanks,
ed
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
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
Re: Core dumps on Current Make World this morning
Same with me. All the machines that I have running Current dumped core at the same place this morning. === share/termcap ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder /dev/null Segmentation fault - core dumped *** Error code 139 Stop in /usr/src/share/termcap. *** Error code 1 For a couple of days now, I haven't been able to use vi because it also dumps core on all the machines except the only one that was able to build world and a new kernel yesterday, just good timing I guess. I haven't seen this on the list. Thanks, ed 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
RE: Core dumps on Current Make World this morning
same here as well... i did a make -k buildworld and that worked for me/.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew Jacob Sent: Tuesday, January 02, 2001 1:06 PM To: Charlie Root Cc: [EMAIL PROTECTED] Subject: Re: Core dumps on Current Make World this morning Same with me. All the machines that I have running Current dumped core at the same place this morning. === share/termcap ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder /dev/null Segmentation fault - core dumped *** Error code 139 Stop in /usr/src/share/termcap. *** Error code 1 For a couple of days now, I haven't been able to use vi because it also dumps core on all the machines except the only one that was able to build world and a new kernel yesterday, just good timing I guess. I haven't seen this on the list. Thanks, ed 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: 20010101: ex and vi were broken by some changes to sys/queue.h. If you have a bad vi (and are getting core dumps when building termcap), you can work around this problem by adding -k to your command line. This will cause the build to complete and install a new vi. Once that's done, you can rebuild again without the -k to pick up anything that might have been ignored by the -k option. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
Ta-da! In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: 20010101: ex and vi were broken by some changes to sys/queue.h. If you have a bad vi (and are getting core dumps when building termcap), you can work around this problem by adding -k to your command line. This will cause the build to complete and install a new vi. Once that's done, you can rebuild again without the -k to pick up anything that might have been ignored by the -k option. 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
Re: Core dumps on Current Make World this morning
:Ta-da! : : : In message [EMAIL PROTECTED] Matthew Jacob :writes: : : Same with me. : : This sounds like a job for Captain UPDATING: : : 20010101: : ex and vi were broken by some changes to sys/queue.h. If : you have a bad vi (and are getting core dumps when building : termcap), you can work around this problem by adding -k to : your command line. This will cause the build to complete : and install a new vi. Once that's done, you can rebuild again : without the -k to pick up anything that might have been : ignored by the -k option. Why in (insert favorite deity)'s name does ex and vi depend on sys/queue.h ? -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
Why in (insert favorite deity)'s name does ex and vi depend on sys/queue.h ? Oh, christ, who knows? I just saw the new David Mamet film "State Main"... in one scene, Alec Baldwin has just crashed a stationwagon and flipped it, wiping out the only stoplight in this town. he crawls out of the wreckage, lounges against the car and says, "Well... that happened." Thie sys/queue.h is probably of the same order. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED] Matt Dillon writes: : Why in (insert favorite deity)'s name does ex and vi depend on : sys/queue.h ? Because it does. :-) Lots of places in the userland tree use it. phk committed a fix to vi that broke vi, and that's the problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir make obj make depend make all install fix the problem? Two buildworlds seems like a big sledgehammer when a small tap with a 2oz would do :-) 20010101: ex and vi were broken by some changes to sys/queue.h. If you have a bad vi (and are getting core dumps when building termcap), you can work around this problem by adding -k to your command line. This will cause the build to complete and install a new vi. Once that's done, you can rebuild again without the -k to pick up anything that might have been ignored by the -k option. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED], Matt Dillon writes: :Ta-da! : : : In message [EMAIL PROTECTED] Matthew Jacob writes: : : Same with me. : : This sounds like a job for Captain UPDATING: : : 20010101: : ex and vi were broken by some changes to sys/queue.h. If : you have a bad vi (and are getting core dumps when building : termcap), you can work around this problem by adding -k to : your command line. This will cause the build to complete : and install a new vi. Once that's done, you can rebuild again : without the -k to pick up anything that might have been : ignored by the -k option. Why in (insert favorite deity)'s name does ex and vi depend on sys/queue.h ? Actually they don't, they depend on db1.85's "mpool" which depends on sys/queue.h since it lives in libc. vi/ex comes with their own copy of sys/queue.h -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED] "Rodney W. Grimes" writes: : This sounds like a job for Captain UPDATING: : : Don't you just need to rebuild vi/ex? Ie would not: : cd /usr/src/usr.bin/vi; : make cleandir make obj make depend make all install : fix the problem? : : Two buildworlds seems like a big sledgehammer when a small tap with : a 2oz would do :-) If someone with a bad vi tries this and it works, I'll change it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED], "Rodney W. Grimes" writes : In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir make obj make depend make all install fix the problem? Two buildworlds seems like a big sledgehammer when a small tap with a 2oz would do :-) It's actually libc you need to reinstall (unless your vi/ex is statically linked). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Core dumps on Current Make World this morning
In message [EMAIL PROTECTED], "Rodney W. Grimes" writes : In message [EMAIL PROTECTED] Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir make obj make depend make all install fix the problem? Two buildworlds seems like a big sledgehammer when a small tap with a 2oz would do :-) It's actually libc you need to reinstall (unless your vi/ex is statically linked). Okay... cd /usr/src/lib/libc; make cleandir make obj make depend make all install -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
