CVSup core dumps: a work-around
Wow, you guys have been busy while I was asleep! Thanks for the reports, and for the diagnosis already done by Marcel, Luoqi, and others. If you are stuck with a kernel that can't run CVSup, I believe you can work around the problem by adding "@M3novm" to the cvsup command line. Add it anywhere on the command line -- its position doesn't matter. Also, I recommend that you _not_ try to rebuild CVSup and/or Modula-3 from the sources at this time. I suspect Modula-3 is broken because of the changed size of the jmp_buf type in -current. (The M3 runtime thinks it knows how big a jmp_buf is.) This shouldn't affect old binaries, but it will bite you if you try to rebuild from the sources. I'll commit a patch as soon as I can, but I am on some other deadlines and it might take me a day or two. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
On Mon, 4 Oct 1999, John Polstra wrote: > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. > It works here with world/kernel built this morning from sources cvsup'd at 0100 EDT from cvsup6.freebsd.org. > - what is the output from "cvsup -v"? earth:~# cvsup -v CVSup client, GUI version Software version: REL_16_0 Protocol version: 16.0 http://www.polstra.com/projects/freeware/CVSup/ Report problems to [EMAIL PROTECTED] earth:~# > - is "cvsup" a static binary or is it dynamically linked? earth:~# file /usr/local/bin/cvsup /usr/local/bin/cvsup: FreeBSD/i386 compact demand paged executable earth:~# ldd /usr/local/bin/cvsup ldd: /usr/local/bin/cvsup: not a dynamic executable (same on all versions) > - did you build it, or did you simply install a binary? no problems with the one retreived using /usr/ports/net/cvsup-bin: earth:/usr/ports/distfiles# md5 cvsup-freebsd-ix86-aout-16.0.tar.gz MD5 (cvsup-freebsd-ix86-aout-16.0.tar.gz) = 57c25981d3c1d82a79b9ae18aaea715b earth:/usr/ports/distfiles# nor from one pkg_add 'ed from ftp://ftp.freebsd.org/pub/FreeBSD/packages/All/cvsup-bin-16.0.tgz : earth:~# md5 cvsup-bin-16.0.tgz MD5 (cvsup-bin-16.0.tgz) = 3e60e196c8ed9f7dac3f145bd72ac536 earth:~# > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz > This one works without fault also. - Chris D. Faulhaber <[EMAIL PROTECTED]> | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
John, > Also, for those of you who are experiencing problems: Please state > as precisely as possible: I have Oct 4 9pm PDT -current on K6 and SMP PPro machine. CVSup coredumps on K6 machine reliably(?) but it works on SMP PPro machine. I tried both 16.0/15.2(? previous one) packages. Both are the same result. Someone said that it works under truss. It did work with my K6 machine. It smells like something uninitialized is used? > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz Great! I was trying to rebuild CVSup by myself, besides I misplaced aout gdb somewhere As your CVSup web page says, it wasn't that straightforward ;-) Thanks Tammy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
John Polstra <[EMAIL PROTECTED]> writes: > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. I don't have access to the machine right now, but I installed the cvsup-bin (both GUI and non-GUI versions) and both core dumped for me. Both versions were obtained from ftp://ftp.freebsd.org/pub/FreeBSD/development/CVSup/binaries This is on the latest -current (as of 9PM Oct 4, 99). Running it under truss helps with the core dump, but runs out of swap space very quickly. Truss keeps complaining about free()'ing a pointer that does not point to allocated memory. If you want more details, I shall be happy to provide them this evening. Hope this helps, Regards, Rajappa -- <[EMAIL PROTECTED]> a.k.a. Rajappa Iyer.New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
Fwiw, the problem seems to have disappeared over here. I'll check at home later. FreeBSD hal.mpn.cp.philips.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Oct 5 09:36:29 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/HAL i386 Cheers, -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Not for me. (was: CVSup core dumps)
Just an anti-me too.
Static cvsup works perfectly for me (installed from ports cvsup-bin on
Sept 9th).
I run it both on my dumb terminal and on my X display.
(My X configuration is XFree86 3.3.5, Gnome/Enlightenment [all built
Sept 9th after a make world]).
My shell is tcsh 6.09 (built Sept 1st).
I have never had cvsup-bin core dump.
I have built the world twice since the signal changes and am currently
running on my build which completed about 36 hours ago.
localhost# {8} cvsup -v
CVSup client, GUI version
Software version: REL_16_0
Protocol version: 16.0
http://www.polstra.com/projects/freeware/CVSup/
Report problems to [EMAIL PROTECTED]
localhost# {9}
On Mon, 4 Oct 1999, John Polstra wrote:
> I've seen a few reports that CVSup has suddenly started dumping
> core on a segmentation violation under -current, but I need more
> information. For starters, I would like to know whether the static
> binary (ports/net/cvsup-bin) works or not under the very latest
> -current on the i386. Could somebody please check that and report
> back to the list? I can't sacrifice my i386 -current machine to the
> cause right now.
>
> Also, for those of you who are experiencing problems: Please state
> as precisely as possible:
>
> - which vintage of -current are you running?
> - what is the output from "cvsup -v"?
> - is "cvsup" a static binary or is it dynamically linked?
> - did you build it, or did you simply install a binary?
> - if you built it, when did you build it?
>
> Note, you are going to have trouble getting much out of the core dumps
> from the binaries, because they're a.out. I've placed an unstripped
> ELF binary here if you'd like to help out by getting a stack trace:
>
> http://www.freebsd.org/~jdp/cvsup-16.0.gz
>
> The compressed file is about 2.3 MB in size.
>
> John
>
--
/===\
| Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] |
\===/
"If it is true that our Universe has a zero net value for all conserved
quantities, then it may simply be a fluctuation of the vacuum of some
larger space in which our Universe is imbedded. In answer to the
question of why it happened, I offer the modest proposal that our
Universe is simply one of those things which happen from time to time."
E. P. Tryon from "Nature" Vol.246 Dec.14, 1973
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
John Polstra wrote: > > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. I received 3 reports on cvsup dumping core. At least 2 involved static aout binaries. The third was solved by changing which shell was running the script containing cvsup. (???) > For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. It coredumps. See below. > > - which vintage of -current are you running? FreeBSD scones.sup.scc.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #17: Mon Oct 4 10:33:12 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/SCONES i386 > - what is the output from "cvsup -v"? *** *** runtime error: ***Segmentation violation - possible attempt to dereference NIL ***pc = 0x2f *** Abort trap (core dumped) > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: Great! I'll get to it. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
On Tue, Oct 05, 1999 at 08:33:54AM +0200, Mark Murray <[EMAIL PROTECTED]> wrote: > > I've seen a few reports that CVSup has suddenly started dumping > > core on a segmentation violation under -current, but I need more > > information. For starters, I would like to know whether the static > > binary (ports/net/cvsup-bin) works or not under the very latest > > -current on the i386. Could somebody please check that and report > > back to the list? I can't sacrifice my i386 -current machine to the > > cause right now. > > The static binary seems to be OK an a 3-day-old CURRENT. And as opposite, the cvsup 16.0 static a.out binary, downloaded a day ago from ftp.freebsd.org dumps reliably core for me. I'm sorry, can't provide any info yet because it's my home machine. The machine runs also 3 day old -current, perhaps with deviation of some 12 hours or so, can't remember. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
> I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. The static binary seems to be OK an a 3-day-old CURRENT. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
My machine is dual boot and I don't have time to reboot now. (I need to get some sleep.) I'll provide what information I can quickly and will test things further tomorrow evening. I was seeing the core dumps from gui cvsup. My current was a couple different cvsup runs on Saturday and Sunday. I am using the static binary installed from the ports collection. I don't have a date or version right now, but seem to recall it being 16.0. As others have mentioned, running cvsup under truss works. I'll let you know more tomorrow night if there is anything I can add. Jim Bloom [EMAIL PROTECTED] John Polstra wrote: > > I've seen a few reports that CVSup has suddenly started dumping > core on a segmentation violation under -current, but I need more > information. For starters, I would like to know whether the static > binary (ports/net/cvsup-bin) works or not under the very latest > -current on the i386. Could somebody please check that and report > back to the list? I can't sacrifice my i386 -current machine to the > cause right now. > > Also, for those of you who are experiencing problems: Please state > as precisely as possible: > > - which vintage of -current are you running? > - what is the output from "cvsup -v"? > - is "cvsup" a static binary or is it dynamically linked? > - did you build it, or did you simply install a binary? > - if you built it, when did you build it? > > Note, you are going to have trouble getting much out of the core dumps > from the binaries, because they're a.out. I've placed an unstripped > ELF binary here if you'd like to help out by getting a stack trace: > > http://www.freebsd.org/~jdp/cvsup-16.0.gz > > The compressed file is about 2.3 MB in size. > > John > -- > John Polstra [EMAIL PROTECTED] > John D. Polstra & Co., Inc.Seattle, Washington USA > "No matter how cynical I get, I just can't keep up."-- Nora Ephron > > 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: CVSup core dumps
I've seen a few reports that CVSup has suddenly started dumping core on a segmentation violation under -current, but I need more information. For starters, I would like to know whether the static binary (ports/net/cvsup-bin) works or not under the very latest -current on the i386. Could somebody please check that and report back to the list? I can't sacrifice my i386 -current machine to the cause right now. Also, for those of you who are experiencing problems: Please state as precisely as possible: - which vintage of -current are you running? - what is the output from "cvsup -v"? - is "cvsup" a static binary or is it dynamically linked? - did you build it, or did you simply install a binary? - if you built it, when did you build it? Note, you are going to have trouble getting much out of the core dumps from the binaries, because they're a.out. I've placed an unstripped ELF binary here if you'd like to help out by getting a stack trace: http://www.freebsd.org/~jdp/cvsup-16.0.gz The compressed file is about 2.3 MB in size. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
On Fri, Oct 01, 1999 at 05:57:14PM -0500, Chris Costello wrote: >Try ``gdb cvsup cvsup.core'' jos:/tmp# file cvsup.core cvsup.core: lif file jos:/tmp# gdb /usr/local/bin/cvsup cvsup.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... "/usr/local/bin/cvsup": not in executable format: File format not recognized "/tmp/cvsup.core" is not a core dump: File format not recognized (gdb) q The GUI version runs fine under truss tho. And the non-GUI version runs fine too, no truss'ing needed. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CVSup core dumps
I updated yesterday, installed the world and a new kernel. That all worked. Today when I run cvsup with the same supfile I used yesterday I get a core dump: # cvsup /root/current-supfile *** *** runtime error: ***Segmentation violation - possible attempt to dereference NIL *** Abort trap (core dumped) # cvsup /root/current-supfile If I truss it, with truss cvsup supfile, it works. # file cvsup.core cvsup.core: data # gdb cvsup.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... "/usr/ports/lang/modula-3/cvsup.core": not in executable format: File format not recognized (I'm in that directory in order to rebuild cvsup for this build to get cvsup working again, but I can't compile modula-3...). Is there a new static binary to use? I thought the problem was my hostname, which was null, but I went ahead and set that (this is on a laptop doing DHCP). TIA, ==Leonard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
On Fri, Oct 01, 1999, Leonard Sitongia wrote: > # gdb cvsup.core > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > > "/usr/ports/lang/modula-3/cvsup.core": not in executable format: File format not >recognized Try ``gdb cvsup cvsup.core'' -- |Chris Costello <[EMAIL PROTECTED]> |If you're not part of the solution, be part of the problem! `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup core dumps
Leonard Sitongia wrote: > > Is there a new static binary to use? > No. Using an old one should fix this. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
