Hi,
I'm having problems with Parrot Segfaulting. What is the most likely
line of attack to find out what the cause is ( gdb, parrot debugger,
praying, etc.). I'm not a C programmer but I read it fairly well and it
is a lot of years since I last used a debugger. My source tree was
updated from CVS
Committed as r10566 & r10567.
-J
--
Rob Kinyon <[EMAIL PROTECTED]> writes:
> On 12/16/05, Ovid <[EMAIL PROTECTED]> wrote:
>> Minor nit: we're discussing to the relational algebra and not the
>> relational Calculus (unless the topic changed and I wasn't paying
>> attention. I wouldn't be surprised :)
>
> Algebra, in general, is a s
On Dec 18, 2005, at 10:58, Steve Gunnell wrote:
Hi,
I'm having problems with Parrot Segfaulting. What is the most likely
line of attack to find out what the cause is ( gdb, parrot debugger,
praying, etc.).
gdb and or valgrind --tool=memcheck
Be sure to use always a recent svn c
Hi,
I get some strange behaviour in the attached code snippet.
The problem is with the lines marked with a '*'. If the global 'r' is
stored into $P0,
and in the second marked line it is called, the output of the print
statements furhter below
is:
Lua_Proto_2_0
2
instead of the expected
1
2
-BEGIN PGP SIGNED MESSAGE-
Moin,
since no one commented on rewritten my graph-usage package I have gone
ahead and uploaded it to CPAN as Graph::Usage.
Now you should be able override the detectionlogic and create graphs from
usage/dependency trees as you like :)
If you have any questi
I have occasionally felt it would be nice to be able to distinguish
between shifting an explicit undef value off an array and calling shift()
on an empty array without having to test the length of the array. Is that
likely to fall out of any of the current thinking? I do not want shift()
on an em
Committed as r10571. I decided not to use Module::Pluggable at this
time as it tries to loading things like the 'hints' modules for all
platforms.
-J
--
> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
PS> I have occasionally felt it would be nice to be able to
PS> distinguish between shifting an explicit undef value off an array
PS> and calling shift() on an empty array without having to test the
PS> length of the array. Is that lik
On Sat, 2005-12-17 at 17:27 -0800, Darren Duncan wrote:
> 3. A flag that says we know that some operation failed, such as would
> be exploited in the " err "
> situations.
> This concept is like an exception which isn't thrown but returned.
"Dropping" an exception, perhaps? :)
> 1. I accept th
On 12/18/05, demerphq <[EMAIL PROTECTED]> wrote:
> On 12/17/05, chromatic <[EMAIL PROTECTED]> wrote:
> > On Saturday 17 December 2005 08:23, demerphq wrote:
> >
> > > It seemed to me that
> > > a better patch would be to change the way harness handles directives
> > > so it recognizes TODO & SKIP a
11 matches
Mail list logo
