This is exactly what I was looking for, thanks!
Looks like the problem was wxvault.dll by Wave Systems.
Baldur
On Sun, Aug 29, 2010 at 09:28:07PM +0100, Dave Korn wrote:
> On 27/08/2010 21:44, mike marchywka wrote:
> > On 8/27/10, Baldur Gislason wrote:
>
> >> Hi, what tool is best to track down
On 27/08/2010 21:44, mike marchywka wrote:
> On 8/27/10, Baldur Gislason wrote:
>> Hi, what tool is best to track down what BLODA is causing fork failures on
>> my Cygwin installation?
> There may be a sysinternals tool, I use those to track down open handles
> that have been a problem on earlier
On 2010-08-27 21:22Z, Baldur Gislason wrote:
> I am attempting to diagnose why fork() fails during the cygwin installation.
> It looks like some kind of BLODA may be causing this, per documentation, but
> obviously, the list of known troublemakers in the documentation does not
> cover all troublema
I am attempting to diagnose why fork() fails during the cygwin installation.
It looks like some kind of BLODA may be causing this, per documentation, but
obviously, the list of known troublemakers in the documentation does not
cover all troublemakers and I'd like to trace what is going on.
Baldur
Since no one replied, perhaps you could supply more details.
What exactly are you trying to do and what happens?
There may be a sysinternals tool, I use those to track down open handles
that have been a problem on earlier systems.
On 8/27/10, Baldur Gislason wrote:
> Hi, what tool is best to tr
Hi, what tool is best to track down what BLODA is causing fork failures on my
Cygwin installation?
Baldur
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwi
6 matches
Mail list logo
