At random times after several hours of system operation we are
experiencing termination of Dev32 due to SIGBUS. My search through the
QNX4 archives turned up that SIGBUS is generated by NMI. Is NMI the only
event that will trigger SIGBUS?
TIA
David McMillan
Oak Ridge National Laboratory
David McMillan wrote:
At random times after several hours of system operation we are
experiencing termination of Dev32 due to SIGBUS. My search through the
QNX4 archives turned up that SIGBUS is generated by NMI. Is NMI the only
event that will trigger SIGBUS?
Yes, SIGBUS is a reflection of an elicited NMI.
–
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Adam Mallory” <amallory@qnx.com> wrote in message
news:d0skt9$f8$1@inn.qnx.com…
David McMillan wrote:
At random times after several hours of system operation we are
experiencing termination of Dev32 due to SIGBUS. My search through the
QNX4 archives turned up that SIGBUS is generated by NMI. Is NMI the only
event that will trigger SIGBUS?Yes, SIGBUS is a reflection of an elicited NMI.
Which on most board (x86) is a memory parity error.
–
Cheers,
AdamQNX Software Systems
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
Mario Charest wrote:
Yes, SIGBUS is a reflection of an elicited NMI.
Which on most board (x86) is a memory parity error.
Or a watchdog or anything else connected to the NMI.
-Adam
Mario Charest wrote:
Yes, SIGBUS is a reflection of an elicited NMI.
Which on most board (x86) is a memory parity error.
Or a watchdog or anything else connected to the NMI.
-Adam
Adam Mallory wrote:
Yes, SIGBUS is a reflection of an elicited NMI.
What about mapping a physical address space not assigned to mem or any
other device, and accessing it?
Which kind of signal is generated?
Davide
–
/* Ancri Davide - */
Davide Ancri wrote:
Adam Mallory wrote:
Yes, SIGBUS is a reflection of an elicited NMI.
What about mapping a physical address space not assigned to mem or any
other device, and accessing it?
What you suggest could result in either a GPF, perhaps a Page fault,
alignment fault or even a machine check exception. Except for the
machine check and alignment fault, both the GPF and page fault
exceptions result in a SIGSEGV. A machine check would result in a
SIGTRAP while an alignment exception would results in SIGILL.
Which kind of signal is generated?
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>