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

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

1949.0. "Segmentation Fault....Core Dump...?" by OTOOA::OTP149::typhair (dtn633-3761) Tue Jan 31 1995 13:54

Hello...

Quick question or two.

Set up...2100, OSF1 V3.0b, Hubwatch for OSF1, GIGAswitch/FDDI, DEChub 900 
(900EE, 900MX, 900EF, 900TM).

1) I receive a core dump when doing the following, it can be reproduced at 
will.  Any ideas as to what I might check to see if its the configuration I 
have set up or if its a bug?

1a. Go into Hubwatch screen and select the community table and click on the 
Gigaswitch agent.  This displays the front panel of the GIGAswitch/FDDI.

1b. I then double click on the FGL2 (DAS) card in the display to bring up the 
new display with management information.

1c. I then select bridging from the options at the bottom of the screen and 
all the Hubwatch related windows go away.  The message in the decterm window 
simply says I received a "segmentation fault (core dumped)".  

Any ideas for the above, I was also able to do it from another option which I 
didn't note...if it occurs again I'll do so.

Suggestions...

Cheers
Steve
T.RTitleUserPersonal
Name		DateLines
1949.1HUBwatch crash == HUBwatch bug.SLINK::HOODI'd rather be at the PenobscotTue Jan 31 1995 16:4310
>1) I receive a core dump when doing the following, it can be reproduced at 
>will.  Any ideas as to what I might check to see if its the configuration I 
>have set up or if its a bug?

It is a bug.  Whenever HUBwatch crashes, it is a bug.

I'll copy your note to the QAR system.

Tom Hood
HUBwatch
1949.2....life with bugsOTOOA::OTP149::typhairdtn633-3761Wed Feb 01 1995 11:216
...looked like a bug, felt like a bug and yup its a bug.

Thanks for the escalation of it.

Cheers
Steve
1949.3Who should I be in contact with...OTOOA::OTP149::typhairdtn633-3761Thu Feb 02 1995 12:506
I should have mentioned in my previous note that the .1 coniguration is going 
to a customer site for evaluation along with HUBwatch for OSF1.  Who should I 
talk to surrounding potential work-arounds, patches, dates...  

Cheers
Steve
1949.4Who to talk to?SLINK::HOODI'd rather be at the PenobscotThu Feb 02 1995 13:176
The people who can give you official dates, etc are
	Jack NAC::Forrest, product manager
	Bruce LEVERS::Sweet, engineering manager

Tom Hood
HUBwatch
1949.5ThanksOTOU01::TYPHAIRThu Feb 02 1995 23:233
    Thanks
    
    Steve
1949.6Engineering contact...pointer is here.OTOU01::TYPHAIRFri Feb 10 1995 09:4611
    I haven't had any success touching base with the engineering contact 
    who is checking out the problem in .1.  I'll leave a pointer here for 
    the core dump(compressed), in case the engineer is following this note 
    as well.
    
    otou01::disk$user3:[typhair]core.z
    
    FYI...I'll update this note with the resolution upon completion.
    
    Cheers
    Steve
1949.7Just a reminder...SLINK::HOODThis is my new personal name for NotesFri Feb 10 1995 11:317
Just a reminder.  Bugs reported here *may* get fixed in the next release.
But if you need special case code, this isn't the place to report problems.

Anyway, the bug in .0 will be fixed in V4.0

Tom Hood
HUBwatch