[nos-bbs] JNOS crash every hour or so.

[Bob Tenty]

Run the gdb debugger as something goes out of bounds as it
looks like it.

 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.

Mail that info to Maiko


Bob VE3TOK


On 14-01-19 07:10 PM, Wm Lewis wrote:
> Well, the latest round of JNOS crashes all give a common error.
>  
> 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"
>  
> Here are the last three I caught and wrote down.
>  
>  
> **** glibc detected *** /jnos/jnos: corrupted double-link list:
> 0x0000000000ff0fb0 ****
> **** glibc detected *** /jnos/jnos: malloc(): smallbin double linked
> list: 0x0000000000a87e60 ****
> **** glibc detected *** /jnos/jnos: corrupted double-link list:
> 0x0000000001c6d390 ****
> ** 
> Anyone have a clue where I should begin looking ??
>  
> Bill Lewis / KG6BAJ
> GVCITY node / 44.2.14.1
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20140119/e9f3446b/attachment.html>