[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

80.0. "lat-console & view log => segmentation fault" by EEMELI::SUOMI () Tue Jun 08 1993 12:47

    
    Heips!
    
    I was demoing today cm and whey I tried to say 'view log' to 
    a lat-console connected system I got
    
    longjmp botch
    Segmentation fault
    
    The console line itself works ok.
    
    And telnet- and comm-connected consoles 'view log' works fine.
    
    CM version 1.0.
    
    Anyone seen this before?
T.RTitleUserPersonal
Name		DateLines
80.1What were you doing just before?OPG::SIMONTue Jun 08 1993 13:0417
Hi,
   a few questions:

1) Is it reproducable?

2) What were you trying to view i.e. I assume you had been connected to the     
console of the managed system, done some things to show the people what can be
done in a connect session and then tried to view the log afterwards. 

3) Do you still have the log event and times files for the system that failed,
and if so could I have them.

I have not seen the segmentation fault with the longjump botch message before,
but we are currently looking in to a bug in the C3 display which can cause
segmentation faults in view log.

Cheers Simon....
80.2it is reproducableEEMELI::SUOMIWed Jun 09 1993 07:4026
1) Is it reproducable?

    Yes. 
    
2) What were you trying to view i.e. I assume you had been connected to the     
console of the managed system, done some things to show the people what can be
done in a connect session and then tried to view the log afterwards. 

    That is exactly what I did.
    
3) Do you still have the log event and times files for the system that failed,
and if so could I have them.
    
    No I haven't those files but because I can reproduce this you can
    get similar files from rixrax:/guest (CM_myrsky*). There is also
    the core file.
    
    (I did this again and this time the messages are different than
    yesterday:
    
    # cm
    pid 14392 (cm) was killed on a kernel access, at pc 0x424b64
    Bus error (core dumped)
80.3Please try this for me.OPG::SIMONWed Jun 09 1993 11:326
Hi,
   I am sending you a mail with details of a patch we are testing. I would be
greatful if you could try this out for me. I could not get the same error from
the log file you sent me a pointer to.

Cheers Simon....