perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: [PATCH] Re: t/perl/ithreads.t revisited
Date Wed, 15 Dec 2004 04:19:02 GMT
Steve Hay wrote:

> Nor me till I tried it.  All it does is print an utterly useless message 
> in the console:
> 
>  >perl -e "CORE::dump()"
> 
> This application has requested the Runtime to terminate it in an unusual 
> way.
> Please contact the application's support team for more information.
> 
> perlport does mention it is not implemented, though.

perlbug it? But on the other hand I think it's going to be deprecated in 5.10.

>>"-e line 0" means 
>>that it's a C code :) you could just as well dereference a NULL pointer 
>>for this purpose. or use my module for that :) 
>>http://search.cpan.org/dist/Debug-FaultAutoBT/DumpCore.pm
>> 
>>
> 
> Couldn't build your module on Win32 either :(

This is probably due to the other module in that package :( May be I 
should release it separately. Feel free to send me the error messages 
offlist to see if it's something that can be easily fixed (if you want to 
bother at all).

>>Is it somewhere in SvRV(ERRSV)? After all ERRSV is an object here.
>> 
>>
> 
> I tried sv_dump(SvRV(ERRSV)) and it just showed that it's a hash with 4 
> keys.  Since we're expecting 4 keys anyway (rc, file, line, func), I 
> didn't bother chasing any of them to see if they were it.

Yeah, I did that too. that means that it stores that stringified object 
elsewhere

>>Bizarre. We need to figure out how to reproduce this bug outside modperl 
>>and report to p5p. since this is definitely a bug in perl.
>> 
>>
> 
> Unless, of course, I'm just being really lucky again.  I tried mucking 
> around with the conf files, adding and deleting code here and there and 
> couldn't break it.  I'm also encouraged that the whole test suite works, 
> but you never know...
> 
> I've tried to reproduce this outside of mp2, but haven't had any luck 
> yet.  The attached "Foo" module does some overloaded stringification of 
> an error object and then plays around with threads, much like api.t 
> followed by ithreads.t, but so far "make test" just runs cleanly :(
> 
> Any suggestions how to try to make this sample module break would be 
> welcome.

that would need to be a C code that mixes overload in it. I'll try to 
write one tomorrow. Please remind me if I forget.

-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message