gdb on /usr/bin/perl (or
wherever
it is) to find out what line of the embedded C code it's croaking on,
dump structs, etc.
-Ken
> -Original Message-
> From: Karthika Arunkumar [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 07, 2006 1:27 PM
> To: inline@perl.org
&g
hika Arunkumar [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 07, 2006 1:27 PM
> To: inline@perl.org
> Subject: debugger
>
> HI all,
> I am using inline CPP in my perl program.
> I get a segmentation fault and I am not able to find from
> which line of code
> it occ
rthika Arunkumar [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 07, 2006 1:27 PM
> To: inline@perl.org
> Subject: debugger
>
> HI all,
> I am using inline CPP in my perl program.
> I get a segmentation fault and I am not able to find from
> which line of code
>
On Sat, Oct 07, 2006 at 02:27:16PM -0400, Karthika Arunkumar wrote:
> I am using inline CPP in my perl program.
> I get a segmentation fault and I am not able to find from which line of code
> it occurs. Can anyone suggest me a debugger.
Could you provide some code that illustrates th
HI all,
I am using inline CPP in my perl program.
I get a segmentation fault and I am not able to find from which line of code
it occurs. Can anyone suggest me a debugger.
thanks ,
kararu.
Solved...
Apologies for the baffling mystery of the apparently correct code I posted.
There were function pointers pointing at buggy things. Specifically I forgot to
remove some INLINE_STACK_* macros and boy who knows what those things do to an
internal non-stack-using function.
Once I removed
able to malloc as many bytes
as I want, given they are available? Of course, this only happens when not in
the perl debugger.
Anyway, I'm continuing but just though
s. Otherwise it returns without error. Also as I
said, running it in the debugger returns without error.
--
SV* _dx_merge( SV* isr0SV, SV* isr1SV, int flags, int interval )
{
assert( SvROK( isr0SV ) );
assert( SvROK( isr1SV )
- Original Message -
From: "Ira Woodhead"
.
.
>
> AV* array = newAV();
> av_push(array, newSViv(df));
> av_push(array, newSViv(cf));
> av_push(array, dxSV);
> av_push(array, pxSV);
> av_push(array, newSViv(lastdoc));
> av_push(array, newSViv(corpus_size - lastdoc));
>
> //
o this point, then seg fault occurs
// before caller can continue!
return array;
}
If I run it under the debugger, everything seems fine. The lengths and strings
all add up, no overflows to be seen. The strings inside dxSV and pxSV never are
overflowed because SVGROW makes them more than long
Yeah, I've seen this before, and it's very aggrivating. Probably has
nothing to do with Inline, just C and perl. I'm guessing memory is just
being initialized differently when you're running under the debugger.
My only suggestion is to insert print statements and
Hi guys,
I'm working with Inline C and I have a segmentation fault that occurs in
certain easily reproduced conditions. I can't seem to get any more specific
error messages (such as where the damn thing is happening) because when I put
it into the debugger, it doesn't happen! E
Hi,
yesterday I wrote that I ran into a problem which
stopped my perl debugger.
Here is a short quote of my code which caused the problem:
use Inline Java => 'STUDY',
STUDY => ['JMSEnqueue'] ,
SHARED_JVM => 1;
sub new {
my $class = shift;
return JMSEnq
htm
-Original Message-
From: Williams, Ken [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 11:05 AM
To: 'Patrick LeBoutillier'
Cc: Inline mailing list (E-mail)
Subject: RE: Using the Java debugger
Hmm, it looks like this may not be an Inline::Java problem - even my
He
onday, December 01, 2003 10:50 AM
To: 'Patrick LeBoutillier'
Cc: Inline mailing list (E-mail)
Subject: RE: Using the Java debugger
Hi Patrick,
That technique seems to have worked pretty well. Unfortunately I'm still
working on investigating the same bug, and I think I need a new tool.
ing list (E-mail)
Subject: RE: Using the Java debugger
Ken,
I've never really used the Java debugger so I'm no expert, but try this
patch and see if it can get you by for now. If it works I'll
make an option out of it.
It basically changes Inline::Java so that it starts the deb
Ken,
I've never really used the Java debugger so I'm no expert, but try this
patch and see if it can get you by for now. If it works I'll
make an option out of it.
It basically changes Inline::Java so that it starts the debugger
instead of a plain JVM. You will probably n
Here's a minor suggestion: in order to get better debugging (like being able
to dump structures of local variables in the current frame), jdb suggested
that I recompile with the -g switch. It didn't work until I blew away the
_Inline/ directory though, because Inline::Java kept using the older ver
Hi Patrick,
Yeah, this basically works - I'm able to run under the debugger and set a
breakpoint in my code. I upped STARTUP_DELAY to a couple thousand seconds.
I had to switch over from JNI mode to client-server mode, and I have no idea
whether it's feasible in general to debug java
"Williams, Ken" <[EMAIL PROTECTED]> writes:
> Thanks, Patrick, I'll give it a try.
>
> It'll be a little difficult because my main script calls various Java
> methods in semi-complicated ways, so I'll essentially have to replicate my
> entire perl script in Java.
>
> I wonder if there would be a
Inline mailing list (E-mail)
Subject: Re: Using the Java debugger
Ken,
That's a great question. There's probably no way to run everything through
the Java debugger, but it should be fairly straitforward to run the
generated Java code outside of Inline::Java.
Your Java classes shou
Ken,
That's a great question. There's probably no way to run everything through
the Java debugger, but it should be fairly straitforward to run the
generated Java code outside of Inline::Java.
Your Java classes should be in _Inline/lib/auto//,
being a mangled form of your script na
Hi,
I've got some Inline::Java code that's throwing itself at the mercy of the
infinite loop gods. Is there any way to use the Java debugger (jdb) or
similar to step through the java portions? Or guidelines for figuring out
how to do it manually with the stuff in the _Inline/ directory?
-Ken
On Tue, Aug 26, 2003 at 11:45:56AM +0530, Jason E. Stewart wrote:
> My current problem (in this email anyway) is that I like using the
> Perl debugger to explore how new modules work, but when I try my code
> with AUTOSTUDY in the debugger I get stuck in an infinite loop. If I
>
Hi,
I'm in need of a Java/Perl solution, and have been trying Java.pm but
hit some snags, and am now looking at Inline::Java - it's very
impressive.
My current problem (in this email anyway) is that I like using the
Perl debugger to explore how new modules work, but when I try my
25 matches
Mail list logo
