You might check why you are not getting a core dump.
man limit for checking system limits that may prevent it. Make
sure that the current working directory is writeable. Be sure
you are not running Netscape as root. Are you running on a Sparc
or other hardware? Do you have the latest recommended patches
installed? I believe that there may be a later version of
netscape which might be better (then again, it may not be).
Speaking only for myself,
> I get bus errors all the time with Solaris 7 & Netscape Nav 4.61. And there's
> no core file being dumped, so the suggestions below don't help.
> > > > I get this error while processing some medical imaging data on a SunOs
> > > > 5.5.1 box.
> > > > Is it a hardware problem or a software problem? (What can I do to find
> > > > out?)
> > > > Some posts in other newsgroups implied one should look at the core file
> > > > with a de*; if you think I should do that, could you point me to a
> > > > reference? (I've never done it before.)
> > > > Thanks,
> > > > sjfromm
> > > > Sent via Deja.com http://www.veryComputer.com/
> > > > Before you buy.
> > > I don't really knw what this problem means. But I've got it 2 Years ago
> > > with solaris and netscape navigator. At this time I also thought that it
> > > were hardware problems. But in some newgroups I've been told that this is
> > > a software problem.
> > > I can't tell you more, but don't worry about your hardware.
> > > cu
> > I suspect that if you had a hardware error you would see the problem
> > when you ran other
> > applications, not just this one.
> > To diagnose you might do something like:
> > run the "file" command against the core file, from that you can
> > determine which binary
> > actually generated the core file.
> > (assuming you don't have any other de* available) the next step
> > would be to
> > run adb against the file (if the core dump is from application "fred"
> > the command
> > would look like this: "adb fred core"). Drink some really strong
> > coffee and read the
> > man page for adb, for more details.
> > At the very least, after you have it loaded in adb you could examine the
> > call stack
> > and registers ($c and $r from within adb should get you this info.
> > If it isn't a home grown app, contact the vendor. If it IS home grown,
> > track down the
> > source code and the "make" files used to create it.
> > (assuming the binary isn't stripped of symbols) You could then run "nm"
> > against the
> > binary to determine external entry points and their names, this and the
> > info from
> > adb should get you in the general ballpark and give you some idea of
> > what is going on
> > Good Luck!