Hi Mattia, hi all,
Mattia Barbon wrote:
So the issue seems to be related to what Mattia mentioned in the old
thread I mentioned in my previous mail. Maybe the Configure flag that
is supposed to disable direct ENV manipulation doesn't work correctly?
This is what I get from perl -V:
I an not sure if -DPERL_USE_SAFE_PUTENV is working or not, but I found
why the workaround was not working. Could you try again with a fresh
SVN checkout? If you are interested, -DDEBUGGING is defined in CCFLAGS,
but Wx overrode CCFLAGS so -DDEBUGGING was not set when building Wx.
Sorry for not answering in a couple of days. I was away on a business trip.
Since then, I've been able compile a debugging perl with the PUTENV
workaround (-DPERL_USE_SAFE_PUTENV isn't propagated from the Configure
command line and needs to be set interactively, it seems) and a
debugging wxWidgets and Wx.pm using the current SVN trunk.
I haven't had time to try to debug my original problem much. I still
expect it to be way beyond the scope of my debugging skills, but given
that I already learned a lot by simply persisting in my attempts,
hopefully I'll be surprised once more ;)
In the end, if I fail to solve this, it means I'll have to rewrite a
large threaded application to not use threads but some sort of
external-process-communicate-by-socket scheme (or so). But that would be
an extremely annoying thing and I'd lose ability of using the Wx thread
events which can be quite handy. Let's not even mention I don't have the
time to reinvent that wheel.
Cheers,
Steffen
