CyberPsychotic wrote:
> however, why would generate bus error? I was told that this happens when
> data is not 'aligned' to 16/32/XX frame. Could anyone please clarify this
> thing?
The 80x86 architecture doesn't require that word accesses are aligned
to 4-byte boundaries (although you can force this to be the case by
setting a flag in the descriptor table entry, Linux doesn't do this).
Searching for SIGBUS in the kernel source code indicates that it
occurs for certain types of access to non-existent pages (although
this more usually results in a SIGSEGV).
In this case, the most likely candidate is trying to access a
non-existent stack page (exception 12).
--
Glynn Clements <[EMAIL PROTECTED]>
