John Polstra writes: > I am trying to understand the CVSup crashes that were reported by some > -current users during the past week or two. I realize the crashes > had to do with changes in the ucontext structure, but I am trying to > understand why those changes mattered. My theory is that the changes > would matter to the old pm3 port, but not to the newer ezm3 port. If > you experienced the crashes, please check which Modula-3 version you > have using pkg_info and let me know.
I didn't get a signal-type crash, but instead just got this: > Edit src/release/doc/en_US.ISO_8859-1/installation/Makefile,v -> Attic > Edit src/release/doc/en_US.ISO_8859-1/installation/alpha/Makefile,v -> Attic > Edit src/release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml,v -> Attic > Edit src/release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml,v -> Attic > Edit src/release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml,v -> Attic > Edit src/release/doc/en_US.ISO_8859-1/installation/common/install.ent,v -> Attic > > > *** > *** runtime error: > *** Value out of range > *** file >"/tmp/a/ports/lang/ezm3/work/ezm3-1.0/libs/libm3/src/uid/Common/TimeStamp.m3", line 70 > *** > > use option @M3stackdump to get a stack trace > Abort (core dumped) This is a -current machine with cvsup-without-gui-16.1f installed (and no separate modula3 stuff). -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
