| |
VE4KLM > JNOS 06.06.21 16:06l 121 Lines 3740 Bytes #999 (0) @ WW
BID : A0I7Y_VE4KLM
Read: GUEST
Subj: How to run debugger while JNOS is running ...
Path: IW8PGT<I3XTY<I0OJJ<LU4ECL<VK2RZ<VK2IO<GB7YEW<VA3TOK<VE4KLM
Sent: 210606/1436z @:VE4KLM.#WPG.MB.CAN.NOAM [Winnipeg] $:A0I7Y_VE4KLM
This is a multi-part message in MIME format.
--------------5C7BFDBA9A908E8D45E81CF9
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Good morning,
I have people reporting crashes off and on, but unless I have detailed
information
on why JNOS crashed, it's hard to provide a fix. It is important to know
why JNOS
crashes, then I can get it fixed, and everyone benefits.
This is a simple procedure. If you are experiencing JNOS crashes more then
you care to deal with at times, then you can run the GDB debugger in another
terminal while JNOS is running already. The procedure is documented below :
1) Get the PID of the jnos process, using the linux command :
ps -ef | grep jnos
2) Once you know what the PID is, then run the gdb debugger as follows :
gdb -p pid
3) GDB will load, JNOS will hang temporarily, and GDB will give you a prompt
at which you should enter the following command :
continue
Then both GDB and JNOS will continue to run again.
4) When a crash occurs, GDB will break out to the prompt again, and JNOS
will hang. Take a screen shot of what GDB printed out, then enter following
command at the GDB prompt :
where
You can also try the following command after that :
back full
Note ALL info that appears, even the JNOS console might have some stuff.
Please send all of that information to me, with a brief explanation of what
might have been going on at the time.
5) If you have JNOS logging in effect, please send me the log file, starting a
little before the crash time, so we can see what might have led up to it.
Thank you, much appreciated. Hope you are all doing 'okay'.
Maiko / VE4KLM
--------------5C7BFDBA9A908E8D45E81CF9
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Good morning,</p>
<p>I have people reporting crashes off and on, but unless I have
detailed information<br>
on why JNOS crashed, it's hard to provide a fix. It is important
to know why JNOS<br>
crashes, then I can get it fixed, and everyone benefits.</p>
<p>This is a simple procedure. If you are experiencing JNOS crashes
more then<br>
you care to deal with at times, then you can run the GDB debugger
in another<br>
terminal while JNOS is running already. The procedure is
documented below :<br>
<br>
1) Get the PID of the jnos process, using the linux command : </p>
<pre class=""> ps -ef | grep jnos
2) Once you know what the PID is, then run the gdb debugger as follows :
gdb -p pid
3) GDB will load, JNOS will hang temporarily, and GDB will give you a prompt
at which you should enter the following command :
continue
Then both GDB and JNOS will continue to run again.
4) When a crash occurs, GDB will break out to the prompt again, and JNOS
will hang. Take a screen shot of what GDB printed out, then enter following
command at the GDB prompt :
where
You can also try the following command after that :
back full
Note ALL info that appears, even the JNOS console might have some stuff.
Please send all of that information to me, with a brief explanation of what
might have been going on at the time.
5) If you have JNOS logging in effect, please send me the log file, starting a
little before the crash time, so we can see what might have led up to it.
Thank you, much appreciated. Hope you are all doing 'okay'.
Maiko / VE4KLM
</pre>
</body>
</html>
--------------5C7BFDBA9A908E8D45E81CF9--
Read previous mail | Read next mail
| |
