perl.xs...char array by rodrigo.bermejo- June 24, 2008 Hello .I have a C function:int MyLib_init(char fnames, int numArgs)That I&39;d like to call from perl.The problem Iam facing is that I&39;ve not been able to represent thechar in xs.---MyLib_init(fnames,numArgs) char fnames << how sould I define it here int numArgs----How should I define a char array using xs Thank you very much.http://www.nntp.perl.org/group/perl.xs/2008/06/msg2469.html Re: Supported Data Types - a reference by Scott Lanning- June 17, 2008 On Mon, 16 Jun 2008, David Hilton wrote:> We recently found a bug in the Quota module (basically, limits much> above a terabyte don&39;t work).>> At this point, I suspect that the problem is in the interface code> (http:search.cpan.orgsrcTOMZOQuota-1.6.2Quota.xs).>> I tried substituting long longs for ints in setqlim. Unfortunately> compilation failed. I&39;ve searched quite a bit, but I haven&39;t been> able to find a reference for data types in XSubs (although it..http://www.nntp.perl.org/group/perl.xs/2008/06/msg2468.html Supported Data Types - a reference by David Hilton- June 16, 2008 We recently found a bug in the Quota module (basically, limits muchabove a terabyte don&39;t work).At this point, I suspect that the problem is in the interface code(http:search.cpan.orgsrcTOMZOQuota-1.6.2Quota.xs).I tried substituting long longs for ints in setqlim. Unfortunatelycompilation failed. I&39;ve searched quite a bit, but I haven&39;t beenable to find a reference for data types in XSubs (although it seemslike most data types from C should work - including 64 bits).I&39;ve never...http://www.nntp.perl.org/group/perl.xs/2008/06/msg2467.html Re: How to get stack info in XS die handler by muppet- June 6, 2008 Tom wrote:> Thanks for that. But that is not what I am looking for really. I> already have a die handler which traps any perl errors. I would like> to access the stack trace from that C code and write it to log.You mean you want a C stack when you crash in XSPerl doesn&39;t know how to do that. Perl knows how to unwind the perl stack,which happens from the Carp modules. Croaks from inside XS code will unwindthe perl stack just fine.If you want a C stack to prepend to the perl stack,..http://www.nntp.perl.org/group/perl.xs/2008/06/msg2466.html Re: How to get stack info in XS die handler by Tom- June 6, 2008 On Jun 5, 4:49 pm, mar...rectangular.com (Marvin Humphrey) wrote:> On Jun 5, 2008, at 5:21 AM, Tom wrote:>> > How will I find ou where the problem occured inside a die handler in> > XS Something like call stack when the exception occured.>> I got the Perl stack into error messages by wrapping a callback to > Carp::confess(). In a perfect world we&39;d get the C stack in there > too, but oh well.>> If you want portability, you have to...http://www.nntp.perl.org/group/perl.xs/2008/06/msg2465.html Re: How to get stack info in XS die handler by Marvin Humphrey- June 5, 2008 On Jun 5, 2008, at 5:21 AM, Tom wrote:> How will I find ou where the problem occured inside a die handler in> XS Something like call stack when the exception occured.I got the Perl stack into error messages by wrapping a callback to Carp::confess(). In a perfect world we&39;d get the C stack in there too, but oh well.If you want portability, you have to special case things depending on whether variadic macros are available. Assuming that they are, in ISO- style, and also that the...http://www.nntp.perl.org/group/perl.xs/2008/06/msg2464.html How to get stack info in XS die handler by Tom- June 5, 2008 How will I find ou where the problem occured inside a die handler inXS Something like call stack when the exception occured. Thanks TThttp://www.nntp.perl.org/group/perl.xs/2008/06/msg2463.html |