Thanks Chuck, that's an excellent idea !
I've also just had a friend here help me remember the assembly
instruction to force a debugger breakpoint, and coded it into a module
which I can call first thing in the XS routine(s) I'm interested in.
$create bpt.mar
.psect pure__code,exe,nowrt,quad
bpt_subr::
.call_entry
bpt
ret
.end
$
This may still have a syntax error, but the idea should work.
"lane DUPHY4.Physics.Drexel.Edu" wrote:
>
> "Craig A. Berry" <[EMAIL PROTECTED]> writes:
> > At 4:58 PM -0500 7/2/01, Patrick Spinler wrote:
> >
> >>I can try to remember how to cause the VMS debugger to
> >>break on entry into a module which hasn't been loaded yet, and thus get
> >>useful debugging info on the VMS-Queue module to Dan S.
> >
> > The general incantation in the debugger is something like
> >
> > set image imagename
> > set module modulename
> > set break Routine_Name
> >
> > You might have to step past the PERL_SYS_INIT in perlmain before you
> > can do that. On occasion I think I've had to step past the loading
> > of the shareable image in DL_VMS and then set break for a particular
> > routine in the image just loaded.
>
> What I usually do is insert a call to gmtime() early in the Perl script,
> then do a
> set image DBGPERLSHR
> set module VMS
> set break PERL_MY_GMTIME
> when the breakpoint fires, then all of the shareable images and
> initialization stuff should be done.
>
> The main reasons for using gmtime is that it's unlikely to be in the
> code you're debugging, it's a simple Perl command that maps to a subroutine
> call, and since I messed with my_gmtime I can remember it easily :)
> --
> Drexel University \V --Chuck Lane
> ======]---------->--------*------------<-------[===========
> (215) 895-1545 _/ \ Particle Physics
> FAX: (215) 895-5934 /\ /~~~~~~~~~~~ [EMAIL PROTECTED]
--
This message does not represent the policies or positions
of the Mayo Foundation or its subsidiaries.
Patrick Spinler email: [EMAIL PROTECTED]
Mayo Foundation phone: 507/284-9485
