On Mon, 7 Dec 2015 10:21:38 +0200
Meir Guttman <mguttm...@gmail.com> wrote:
> Dear DBI users,
>
> I use Perl, DBI and DBD:mysql for years, without a problem. But working on
> my latest project I encounter Perl often, but *not always(!) *crashing with
> the Windows message "Perl interpreter has stopped working". As far as I can
> tell the script runs to its natural end.I must add that together with this
> phenomenon ("Poster hoc ergo prompter hoc...") I get, again some times but
> not always, an out-of-the-blue Devel::Peek report and sometimes two or
> rarely three of those. These I also don't know where did they come from.
>
> - Platform: Win-7 Pro
> - Perl: Strawberry Perl ver. 5.18.2.1.
> - DBI: 1.63
> - DBD::mysql 4.025
>
> I extracted the crash report from the Windows Event log, below. If I
> understand it correctly, the culprit is libmysql__.dll.
> Can somebody give me directions as to how to narrow it down to the package
> and line?
One approach is running the thing with "perl -d". The debugger
may give you a bit more information on where in the perl code
you are failing.
That or start dumping progress statements to stderr before and
after each block of DBI statements that access MySQL. This is
a rather nice example of somplace Log4Perl works nicely: put
"debug" logs with statements and args all over the place.
As a last resort you can use "perl -d" and set DB::Trace = 1.
The problem is that if you're croaking in mysql's dll then
there may not be much you can do about it from Perl's side.
Might be worth checking (or re-installing) the MySQL lib's
and DBD::mysql to make sure they are in sync.
--
Steven Lembark 3646 Flora Pl
Workhorse Computing St Louis, MO 63110
lemb...@wrkhors.com +1 888 359 3508
