Steven J Mackenzie wrote:
>
> Most of the SIGBUS errors that I get are because of my bad programming :)
>
> It means that the program has tried to access memory which it can't, I guess
> pretty much as described by Bug Hunter.
>
> This could happen if the value of a pointer to memory is manipulated badly,
> so that the value represents memory that doesn't exist, and then the program
> tries to see what the pointer is pointing at. Bang.
>
> Bug Hunter wrote:
> >
> > Bus access fault usually means that a program tried to address memory
> > that has either failed (a chip failed), or is not plugged into the PC.
> >
> > What happens is that memory usually provides a ready line back to the
> > processor. The processor will time out waiting for this ready line from
> > non-existant memory and give you a "bus access fault."
> >
> > Under Linux, about the only reason for this is that your memory has some
> > bad spots in it, unless the communicator code programmed around this and
> > set the gdt or ldt itself. (In brief, gdt and ldt are arrays that map
> > physical memory to arbitrary address values.)
> >
> > wade
> >
Thanks a lot for enlightening me, you two. But I still don't understand why
it works on 5.3 and crashes on 6.0. Looks like memory handling changed with
the glibc2.1 version, but then more people should have these crashes.
Confused
tom
--
"Everybody is someone else's newbie." (Marilyn Manson, edited)
Thomas 'Tom' Berger, [EMAIL PROTECTED] No UCE. No spam. 'nuff said.
Questions? Answers! Go Mandrake Answers at http://aolmfaq.tsx.org
