[nos-bbs] Another FC-5 flop

[George (Skip) VerDuin]

This is the second FC-5 incident on my system - it may or may-not be
related to the linux version.
I'll stick with it until the problem is specified in detail - FC-5 may
be too bleeding edge...

I see today Maiko has pre-compiled jnos2.0e versions, and I jumped on
them for use here.
Both the slackware and FC-2 modules SIGSEGV Segmentation Fault -
after printing intro text to console and logging "using new [tun0]
device" while in autoexec.nos processing.
So I inserted gdb to look for the back trace using both versions and got
the same result.

GDB tells me:
       Program received signal SIGSEGV, Segmentation Fault
       0x009b5f09 in __longjmp () from /lib/libc.so.6

upon asking gdb for a back trace - gdb tells me there is an internal
problem with gdb itself "unknown register rule" so I quit.

I'm sorry to not have dug deeper into this before posting a note, but it
looks like FC-5 has significant changes to it over FC-4.
Even effecting the executable.  So much for cross-platform
compatibility?
My guess: I've got an incompatible glibc on my system: glibc2.4-8.  I
believe FC-4 had glibc2.3(something)  
                And it feels similar to the engineering change discussed
earlier.

Perhaps FC-5 for jnos needs to be "put away" for a year to let it
mature?  I'm not comfortable introducing too many "varieties"...

73
de Skip k8rra k


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tapr.org/pipermail/nos-bbs/attachments/20060528/3e7a5d3d/attachment.htm