[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: throw() causing core dumps on sparc
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: throw() causing core dumps on sparc
- From: Michael Coulter <mjc_(_at_)_bitz_(_dot_)_ca>
- Date: Wed, 4 Dec 2002 11:02:43 -0800
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Tue, Dec 03, 2002 at 07:13:18PM -0800, Michael Coulter wrote:
> On Tue, Dec 03, 2002 at 09:23:38PM -0500, Monty Brandenberg wrote:
> > Try passing 'p' as an argument to printf.
> Oops. Fixed that, same problem though.
> And it's not just that code snippet, both c++ based ports
> I've tried running died in the same manner.
Several people have mailed me off list with helpful coding tips.
However it's not just this piece of code. I noticed art just added
a regress test (coincidence ?), so I updated /usr/src/regress and
gave it a whirl.
Here is the last bit:
c++ -O2 -c exceptions.cc
cc -o exceptions exceptions.o
*** Signal 6
Here is the backtrace from gdb on the exceptions binary.
Program received signal SIGABRT, Aborted.
0x8290bf4 in abort ()
#0 0x8290bf4 in abort ()
#1 0x1071f in __terminate ()
#2 0x10733 in __terminate ()
#3 0x11207 in __throw ()
#4 0x10687 in main ()
#5 0x10563 in ___start ()
Is anyone else running -current on sparc able to reproduce this ?