Hi,
I am investigating a problem where the most recent builds of software my
company wrote are causing hard crashes. I’ve tried a lot of different
techniques to try to determine what is crashing, but to no avail.
Then I had a thought, what if the kernel is faulting? Our application is a
Photon based program. If a kernel fault occurs, will it switch back to the
console automatically?
TIA,
Ron
No, but you can specify an option to Proc to direct a crash message to the
serial port and capture it that way via the -o port,baud option.
Also make sure Debugger32 isn’t in your image (unless you specify the -s
option to send its output also to the serial port) otherwise you may never
see anything since we’d be in the debugger on the console.
-Adam
Ron Cococcia <ron.nospam@request.nospam.com> wrote in message
news:bgb9vm$1q8$1@inn.qnx.com…
Hi,
I am investigating a problem where the most recent builds of software
my
company wrote are causing hard crashes. I’ve tried a lot of different
techniques to try to determine what is crashing, but to no avail.Then I had a thought, what if the kernel is faulting? Our application is
a
Photon based program. If a kernel fault occurs, will it switch back to
the
console automatically?TIA,
Ron
Adam Mallory <amallory@qnx.com> wrote:
No, but you can specify an option to Proc to direct a crash message to the
serial port and capture it that way via the -o port,baud option.Also make sure Debugger32 isn’t in your image (unless you specify the -s
option to send its output also to the serial port) otherwise you may never
see anything since we’d be in the debugger on the console.
Also, make sure that Dev.ser does NOT take over control of that serial
port as well, or, again, you may never get your output. This may require
modifying your sysinit.node file to explicitly tell Dev.ser which serial
ports to use (it defaults to finding com1 & com2).
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.