[3532] in SIPB bug reports
sun4 7.4G: discuss
daemon@ATHENA.MIT.EDU (yandros@MIT.EDU)
Wed Feb 24 04:53:44 1993
From: yandros@MIT.EDU
Date: Wed, 24 Feb 93 04:53:07 EST
To: bug-sipb@MIT.EDU
Cc: discussers@MIT.EDU
Reply-To: yandros@ATHENA.MIT.EDU
System name: deathtongue
Type and version: SPARC/IPX 7.4G
Display type: Don't know how to determine display type for this machine. (Heh. :)
What were you trying to do?
Find out who enterred the last 30 or so trn's in napalm, even
though I didn't know how the `list' command took it's args.
What's wrong:
I started discuss with `discuss napalm', then I issued a
couple abortive attempts at an `ls' command which got blown
out of my scrollback buffer by `help ls', and then:
discuss: status
Discuss version 1.6.
Attending Flaming_Thoughts (napalm) meeting. (Public.)
Transaction 4733 of 4738.
discuss: list 4700-
discuss (list): Premature end of block Can't get meeting info
discuss: list 4700-4738
discuss (list): No transactions selected
discuss: list
discuss (list): Premature end of block Can't get meeting info
discuss: g napalm
Flaming_Thoughts meeting: 5 new, 4738 last.
discuss (goto): Premature end of block Looking for non-deleted transaction
discuss: list 4700-4738
discuss (list): Premature end of block Can't get meeting info
discuss:
discuss: status
Discuss version 1.6.
Segmentation fault (core dumped)
The original core file is in dt:/usr/tmp/core.y.discuss, where
it will stay indefinately. A gzip'd (gunzip in
/afs/sipb/project/gnu/bin, in case you didn't know) copy is
available in ~yandros/tmp/core.discuss.z - I left the original
because I know that there is weirdness associated with sun
coredumps, and I know I don't understand it. :-)
What should have happened:
Not a core dump. Something I did seems to have managed to get
it into an inconsistent state, but I have no idea what.
Please describe any relevant documentation references:
>where discuss
/mit/sipb/@sys/discuss
/usr/athena/bin/discuss
/usr/bin/X11/discuss
