From owner-freebsd-hackers Tue Nov 13 11:50:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [128.29.154.90]) by hub.freebsd.org (Postfix) with ESMTP id 5A1E737B405 for ; Tue, 13 Nov 2001 11:50:46 -0800 (PST) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id fADJoi120787 for ; Tue, 13 Nov 2001 14:50:44 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id fADJohs01452 for ; Tue, 13 Nov 2001 14:50:43 -0500 (EST) Received: from dhcp-48-37.mitre.org (128.29.48.37) by mailhub2.mitre.org with SMTP id 8348314; Tue, 13 Nov 2001 14:50:17 -0500 Message-ID: <3BF179CA.14EC4554@mitre.org> Date: Tue, 13 Nov 2001 14:51:38 -0500 From: "PSI, Mike Smith" Organization: The MITRE Corporation X-Mailer: Mozilla 4.76 [en]C-20010313M (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: C++ and ISO sockets Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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) mlsmith@mitre.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message