by sjfr.. » Thu, 25 May 2000 04:00:00
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.
by lmack.. » Thu, 25 May 2000 04:00:00
you can do this
# file core
core: ELF 32-bit MSB core file SPARC Version 1, from 'dtwm'
This is what it would look like.
> 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.
by Robert Ulme » Thu, 25 May 2000 04:00:00
> 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.
by Joe Durusa » Thu, 25 May 2000 04:00:00
man core
The most popular cause of this problem is a prog. that has
been ported from windoz and has used packed structures or some such.
Sparc hardware does not have the capability of reading data from
misaligned memory addresses. You might look into whether this prog
has run before, and under what circumstances. It could be, of course,
that the data input to the prog is mangled in some way, but that's
more unlikely.
Speaking only for myself,
Joe Durusau
> 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.
by Neil W Ricker » Thu, 25 May 2000 04:00:00
by Barry Margoli » Thu, 25 May 2000 04:00:00
More technically, it's the hardware detecting what is most likely aQuote:>In my experience, this is usually a data alignment error.
>Technically it is a hardware problem that was triggered by a software
>problem.
--
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
by Tom Anderso » Fri, 02 Jun 2000 04:00:00
> > 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
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!
by Mimr » Tue, 06 Jun 2000 04:00:00
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!
by Joe Durusa » Wed, 07 Jun 2000 04:00:00
Speaking only for myself,
Joe Durusau
> 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!
by sjfr.. » Thu, 08 Jun 2000 04:00:00
> >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?)
> In my experience, this is usually a data alignment error.
> Technically it is a hardware problem that was triggered by a software
> problem.
Sent via Deja.com http://www.deja.com/
Before you buy.
by Bob Beatt » Fri, 09 Jun 2000 04:00:00
We also experienced Bus Errors with Netscape. They would happen
whenever it tried to start Java, but only if Netscape was being
run from a PC in an Xwin32 CDE window. It never crashed if it
was run from the Solaris console.
The problem went away after I added a font server (the Solaris 2.7 host)
to the Xwin32 font path. (Other applications had been giving font-related
warnings.)
Hope this helps
Bob Beattie
>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
1. NCSA htppd 1.5 gives Bus Error (core dumped) !!
I've tried the newest NCSA httpd on my Sparc
(httpd_1.5a-export_solaris2.4_sparc.tar.Z)
and running the binary supplied with the package always results in this:
# uname -a
SunOS palmetto 5.5 Generic sun4m sparc SUNW,SPARCstation-10
# ./httpd
Bus Error (core dumped)
#
I know that the supplied binary is intended for Solaris 2.4 so I
recompiled it but I still get the same results with the resulting output
binary.
This seems to be the case with Solaris x86 2.5 as well.
What simple, obvious, no brainer thing have I over looked?!?!?!?
--
------------------------------------------------------------------------
Kevin Martinez | Fry's Electronics: Where
------------------------------------------------------------------------
3. Bus error (core dumped) !please help!
7. java in netscape = bus error core dump
8. How can I login root, from a remote node
12. FreeBSD problem: Bus Error (core dumped) !Please Help!
13. Bus error (core dump) in Solaris 2.5.1