Have a tricky problem. I am developing code to transfer data over AF_ISO family sockets. Standard stuff, socket, bind, etc. Nothing tricky. Being a good little boy I am using C++ (gpp delivered with OS) for transportability (read make sure everyone else faces the same stupid problems I did).
Alas, when it works it works like a champ. But every 2nd, 3rd, execution, the system freezes or crashes (when I've actually gotten feedback it seems to be a page fault in kernel). This happens before I even get to my first line of code (I've put in a "program running" to stdout WITH A FLUSH at the start of my code). The only non-standard library I'm using is -liso. Has anyone ever encountered something like this...don't like user programs crashing the kernel. I hope someone can help because I am really trying to avoid the kernel debugger. I'm convinced it is in the C++ initialization, but why would this only affect subsequent running of the same program? Is there possibly something in -liso that is causing problems? Something that C++ would call on it's own during it's initialization (can't imagine what). I am using FreeBSD 3.2 (no comments please - I've given plenty of "comments" to the powers that be without results). I am currently rewriting it in C to determine if C++ may be the problem. Any clues?? Mike Smith (not THE Mike Smith) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
