ARSperl
view release on metacpan or search on metacpan
html/debug.html view on Meta::CPAN
<BODY BGCOLOR="#FFFFFF">
<H1> How to debug ARSperl </H1>
Because the ARS extension gets loaded into perl dynamically, there
are a few extra steps needed to debug it. You will need to build a separate
perl installation compiled with debugging turned on.
<H3> Steps </H3>
<OL>
<FONT SIZE="+1"> <LI> Configure perl </FONT> <P>
When perl's Configure script prompts you : <BR>
<I> What optimizer/debugger flag should be used? </I><BR>
you should specify -g instead of the default -O. <BR>
It is also usually a good idea to use perl's built in malloc.
The will prevent ARSperl from crashing due to malloc/free bugs. <P>
<FONT SIZE="+1"> <LI> Install perl/Install ARSperl </FONT> <P>
If you're perl install went correctly, ARSperl should automatically
get compiled with the -g switch.<P>
<FONT SIZE="+1"> <LI> Try it out <BR> </FONT> <P>
I use gdb (the gnu debugger) for debugging, but others (like dbx)
will probably work. Debugging ARS involves switching between
html/manual/ds_msgstruct_hash.html view on Meta::CPAN
"messageText" => string,
"usePromptingPane" => integer (boolean: 0 or 1)
}
</PRE>
<B>Notes</B>:
<UL>
<LI>This structure was introduced in ARSperl v1.62.
<LI>The "messageType" string is mapped from status return values.
Typical values are "ok" (which means "note"), "warning",
"error", and "prompt". Since Remedy uses the AR_STATUS codes
as message types instead of providing a distinct decoding in the
API, "0" is translated to "ok" instead of "note".
</UL>
<P>
<HR WIDTH="30%">
<P>
<A HREF="toc.html"><IMG ALT="<--" SRC="arrow.gif" ALIGN=CENTER> Table of Contents </A>
<p>
Last changes to this page 1 Jun 2000 by jcmurphy<BR>
© J.C.Murphy, J.W.Murphy 1997 <address>
( run in 1.167 second using v1.01-cache-2.11-cpan-0b5f733616e )