[Orca-users] Re: Segmentation Fault with 1.35

[jkcummi]

I think I have narrowed the problem down to just ONE of my Solaris 7 
systems.  I am going to go over it with a fine tooth comb today.  It 
is possible that I am missing a patch or something.

I went back and re-installed orca-0.27b2 on the 6 systems which were 
having problems.  5 of the six started working.

I am going to put in the 1.35 updates next to see if that makes them 
break.

-Kyle

--- In orca-users at y..., "jkcummi" <jkcummi at y...> wrote:
> Ok, I did some new testing today.  I tried to use SE 3.0 but it 
does 
> not support Solaris 7.  I also tried to use SE 3.3 but it does not 
> support 32 bit.  (We run Solaris 7 32 bit for application support 
> reasons)
> 
> I guess I am stuck with using SE 3.2.1.
> 
> Is there any additional information I can collect which might point 
> the SE folks at the root cause?
> 
> Thanks for the help in this...
> 
> -Kyle
> 
> --- In orca-users at y..., Blair Zajac <blair at o...> wrote:
> > adlegrand wrote:
> > > 
> > > Kyle,
> > > 
> > >          You seem to have uncovered a bug in the SE toolkit.  
Not 
> the
> > > raw disk code. :(    You have no idea how glad I am about that. 
It
> > > does however strongly resemble the errors that sometimes 
occured 
> in
> > > earlier versions of the RAW DISK code.
> > > 
> > > These occured when the code was trying to identify a raw device 
> like
> > > sd27  which did not exist in the structure GLOBAL_disk_info
> > > [].short_name.  It ended up walking off the end of the array 
into
> > > unallocated memory.
> > > 
> > > You might try it with an earlier version of the SE toolkit. To 
see
> > > if this solve your problem.
> > 
> > Alan,
> > 
> > That's great news!
> > 
> > If we could figure out where this error occurs, we could send in 
a 
> bug
> > report to the SE developers.
> > 
> > Kyle,
> > 
> > You may want to try SE 3.3.
> > 
> > Best,
> > Blair
> > 
> > -- 
> > Blair Zajac <blair at o...>
> > Web and OS performance plots - http://www.orcaware.com/orca/