From owner-freebsd-hackers Mon Mar 19 13:33: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id D913737B724 for ; Mon, 19 Mar 2001 13:32:58 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2JLWa467799; Mon, 19 Mar 2001 16:32:36 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: <005401c0b0b8$1e7f3ca0$6346a8c0@hackthis> Date: Mon, 19 Mar 2001 16:32:36 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: hackthis Subject: RE: gcc and exceptions and frame.c Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The stack trace looks pretty useless because of all these "cannot access memory" messages. Anyway, it seems like your program is dying because of unhandled exception. Either you did not provide the suitable try {} catch construct or bug in GCC or your code prevents DWARF unwinder from finding suitable handler for the exception. It there any particular reason why you are using gcc295 from ports instea= d of FreeBSD stock compiler? Stock compiler does not use DWARF and is supposed t= o handle exceptions correctly, so unless there are some really good reasons, I would recommend you to use the stock compiler. It is hard to say what exactly goes wrong without seeing actual code of you= r program. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message