<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thanks Bob for the info. But, as Murphy's Law would have it, I have followed your instructions and now the BBS seems to be humming right along for several days without crashing.<BR> <BR>So, GDB is running and monitoring and I can't get it to fail.<BR> <BR>Will let you (and Maiko) know if anything happens.<BR> <BR>Bill<BR><BR> <BR>
<DIV>
<HR id=stopSpelling>
Date: Sun, 19 Jan 2014 22:20:16 -0500<BR>From: bobtenty@gmail.com<BR>To: nos-bbs@tapr.org<BR>Subject: Re: [nos-bbs] JNOS crash every hour or so.<BR><BR>
<DIV class=ecxmoz-cite-prefix>Run the gdb debugger as something goes out of bounds as it<BR>looks like it.<BR><BR><PRE style="LINE-HEIGHT: normal; TEXT-TRANSFORM: none; FONT-VARIANT: normal; FONT-STYLE: normal; TEXT-INDENT: 0px; WORD-WRAP: break-word; WHITE-SPACE: pre-wrap; LETTER-SPACING: normal; COLOR: rgb(0,0,0); FONT-WEIGHT: normal; WORD-SPACING: 0px"> Using GDB is easy. With JNOS running already, find out it's pid, using
the linux command, 'ps -ef | grep jnos'. Once you know what the pid is,
then run the gdb debugger something like this :
gdb -p pid
GDB will load, JNOS will hang temporarily, and GDB will suddenly give
you a prompt. Enter the command, 'continue', at the prompt, and JNOS
will continue to run again.
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 type in
the command, 'back full', at the GDB prompt, and note the info that
appears.
</PRE>Mail that info to Maiko<BR><BR><BR>Bob VE3TOK<BR><BR><BR>On 14-01-19 07:10 PM, Wm Lewis wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:BLU170-W50837AA30820727BBFE9DFA9A50@phx.gbl>
<STYLE><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></STYLE>
<DIV dir=ltr>Well, the latest round of JNOS crashes all give a common error.<BR> <BR>About every hour or so (more so during message forwards) my JNOS will crash and the error on the screen always starts with " *** glibc detected *** " Most also reference a "double-linked"<BR> <BR>Here are the last three I caught and wrote down.<BR> <BR> <BR><STRONG><FONT size=4>*** glibc detected *** /jnos/jnos: corrupted double-link list: 0x0000000000ff0fb0 ***</FONT></STRONG><BR><STRONG><FONT size=4>*** glibc detected *** /jnos/jnos: malloc(): smallbin double linked list: 0x0000000000a87e60 ***</FONT></STRONG><BR><STRONG><FONT size=4>*** glibc detected *** /jnos/jnos: corrupted double-link list: 0x0000000001c6d390 ***</FONT></STRONG><BR><STRONG></STRONG> <BR>Anyone have a clue where I should begin looking ??<BR> <BR>Bill Lewis / KG6BAJ<BR>GVCITY node / 44.2.14.1<BR></DIV><BR>
<FIELDSET class=ecxmimeAttachmentHeader></FIELDSET> <BR><PRE>_______________________________________________
nos-bbs mailing list
<A class=ecxmoz-txt-link-abbreviated href="mailto:nos-bbs@tapr.org">nos-bbs@tapr.org</A>
<A class=ecxmoz-txt-link-freetext href="http://www.tapr.org/mailman/listinfo/nos-bbs" target=_blank>http://www.tapr.org/mailman/listinfo/nos-bbs</A>
</PRE></BLOCKQUOTE><BR>
<DIV style="BOTTOM: auto; DISPLAY: none; TOP: 179px; RIGHT: auto; LEFT: 97px" id=ecxtranslator-floating-panel class=ecxtranslator-theme-default>
<DIV id=ecxtranslator-floating-panel-button title="Click to translate"></DIV></DIV><BR>_______________________________________________ nos-bbs mailing list nos-bbs@tapr.org http://www.tapr.org/mailman/listinfo/nos-bbs</DIV> </div></body>
</html>