I'm debugging the tests of a large package of modules that interface to an even-larger C++ package. It was going well until some previously-passing tests began to fail. I profiled a test in an attempt to locate the failure, and --surprise-- the test passed. From this I conclude that there's a race condition somewhere.
No threads.
Given that races tend to be highly context sensitive, I'm looking for hints.
Here's the test driver
use Audio::TagLib;
$proto = 'Audio::TagLib::ID3v2::Frame';
foreach $method (qw{toString}) {
$return = $proto->can($method);
print "$method: ", defined $return ? 'ok' : 'not ok', "\n";
}
Result is "not ok" . With -d:DProf its "ok"
My perl5 (revision 5 version 12 subversion 4) configuration:
osname=linux, osvers=2.6.32-131.2.1.el6.x86_64, archname=i386-linux-thread-multi
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.