Sold. commited as r20532.
-J
--
On Sat, Aug 04, 2007 at 12:57:25PM -0700, chromatic wrote:
> On Thursday 02 August 2007 16:39:07 Joshua Hoblitt wrote:
>
> > Does anyone object to this patch?
> >
> > Index: exceptions.c
> > ===
> > -
On Thursday 02 August 2007 16:39:07 Joshua Hoblitt wrote:
> Does anyone object to this patch?
>
> Index: exceptions.c
> ===
> --- exceptions.c(revision 20408)
> +++ exceptions.c(working copy)
> @@ -771,7 +771,7 @@
> {
Does anyone object to this patch?
Index: exceptions.c
===
--- exceptions.c(revision 20408)
+++ exceptions.c(working copy)
@@ -771,7 +771,7 @@
{
fprintf(stderr, "%s:%u: failed assertion '%s'\n", file, line,
cond);
I've just commit some notes on this into docs/debug.pod along with some
instructions for getting a backtrace with gdb.
It's worth noting that assert() calls abort() while PARROT_ASSERT
currently does not so this change is not really semantically equivalent.
Some people _will want_ a core file as t
very nice -- i could have used that THIS AFTEROON! :)
On Thu, 26 Jul 2007, Andy Lester wrote:
Josh putting in the new backtrace behind my new assertions makes debugging
assertions SO MUCH EASIER.
I'm gonna go s/assert/PARROT_ASSERT/ everywhere.
xoxo,
Andy
P.S. sample
# Received:
# 1..
Josh putting in the new backtrace behind my new assertions makes
debugging assertions SO MUCH EASIER.
I'm gonna go s/assert/PARROT_ASSERT/ everywhere.
xoxo,
Andy
P.S. sample
# Received:
# 1..1
# Backtrace - Obtained 16 stack frames (max trace depth is 32).
# (unknown)
# Parrot_conf
