On Feb 27, Corinna Vinschen wrote:
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
[...]
Of course I'd be interested in your experience with this and in any
BLODA message you get by setting
On 3/30/2012 1:51 PM, Christian Franke wrote:
On Feb 27, Corinna Vinschen wrote:
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
[...]
Of course I'd be interested in your experience with this and
On 2012-03-30 16:15, David Rothenberger wrote:
I link svn against CRYPT32.DLL to use the windows-cryptoapi password
store code in the Subversion source. This is used by svn to encrypt
passwords it stores in the filesystem. Without it, the only choices are
gnome-keyring and kwallet, which aren't
On Tue, Feb 28, 2012 at 10:21:44AM +0100, Corinna Vinschen wrote:
On Feb 27 18:53, David Rothenberger wrote:
On 2/27/2012 4:26 AM, Corinna Vinschen wrote:
Of course this is not foolproof. The only filtered system DLLs so
far are kernel32.dll, ntdll.dll, mswsock.dll, amd ws2_32.dll.
On Mar 21 10:39, Denis Excoffier wrote:
XWin was started with the following command line:
/usr/bin/XWin -emulate3buttons -unixkill :0
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/po8371:0
On Wed, Mar 21, 2012 at 11:43:26AM +0100, Corinna Vinschen wrote:
I added advapi32.dll to the list of ignored DLLs. There's more stuff
starting new threads under the hood than I expected.
Thank you.
Incidentally, why in the quoted message, and also in
On Mar 21 12:04, Denis Excoffier wrote:
On Wed, Mar 21, 2012 at 11:43:26AM +0100, Corinna Vinschen wrote:
I added advapi32.dll to the list of ignored DLLs. There's more stuff
starting new threads under the hood than I expected.
Thank you.
Incidentally, why in the quoted message, and
On Feb 29 11:06, Ryan Johnson wrote:
On 29/02/2012 10:01 AM, Corinna Vinschen wrote:
On Feb 29 09:51, Ryan Johnson wrote:
On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed
On 01/03/2012 4:53 AM, Corinna Vinschen wrote:
On Feb 29 11:06, Ryan Johnson wrote:
On 29/02/2012 10:01 AM, Corinna Vinschen wrote:
On Feb 29 09:51, Ryan Johnson wrote:
On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
On Mar 1 08:19, Ryan Johnson wrote:
I still think reporting specific base collisions during a fork
failure -- or at least detecting their existence and telling the
user to rebase -- would be helpful.
Yes, that could be helpful.
Corinna
--
Corinna Vinschen Please, send
Greetings, Corinna Vinschen!
Yup, confirmed. This occurs on W7/32 as well.
I add shlwapi to the list of filtered DLLs for which no such message is
printed.
Could you please consider making such list configurable, if it's not much of
an issue?
This feature seems to be the reasonable
On Feb 29 02:41, Andrey Repin wrote:
Greetings, Corinna Vinschen!
Yup, confirmed. This occurs on W7/32 as well.
I add shlwapi to the list of filtered DLLs for which no such message is
printed.
Could you please consider making such list configurable, if it's not much of
an issue?
Greetings, Corinna Vinschen!
Yup, confirmed. This occurs on W7/32 as well.
I add shlwapi to the list of filtered DLLs for which no such message is
printed.
Could you please consider making such list configurable, if it's not much of
an issue?
This feature seems to be the reasonable
On 29/02/2012 7:22 AM, Andrey Repin wrote:
do you filter by DLL name or it's full path?
Because, %SystemRoot%\system32\shlwapi.dll is likely to be harmless.
But same name DLL inserted from any other place...
That would be moving beyond mere BLODA and into malware territory. At
that point, just
On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
If you set the environment variable CYGWIN to detect_bloda and then
start a Cygwin process
On Feb 29 09:51, Ryan Johnson wrote:
On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
If you set the environment variable CYGWIN to
On 29/02/2012 10:01 AM, Corinna Vinschen wrote:
On Feb 29 09:51, Ryan Johnson wrote:
On 27/02/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
If
On Feb 27 18:53, David Rothenberger wrote:
On 2/27/2012 4:26 AM, Corinna Vinschen wrote:
Of course this is not foolproof. The only filtered system DLLs so
far are kernel32.dll, ntdll.dll, mswsock.dll, amd ws2_32.dll. If you
playing around with this, and if you find that a core
On Feb 27 20:02, David Rothenberger wrote:
On 2/27/2012 6:53 PM, David Rothenberger wrote:
On 2/27/2012 4:26 AM, Corinna Vinschen wrote:
Of course this is not foolproof. The only filtered system DLLs so
far are kernel32.dll, ntdll.dll, mswsock.dll, amd ws2_32.dll. If you
playing
Greetings, Corinna Vinschen!
Yup, confirmed. This occurs on W7/32 as well.
I add shlwapi to the list of filtered DLLs for which no such message is
printed.
Could you please consider making such list configurable, if it's not much of
an issue?
This feature seems to be the reasonable way for
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
If you set the environment variable CYGWIN to detect_bloda and then
start a Cygwin process (bash or so), then Cygwin will detect two types
of
On 2/27/2012 7:26 AM, Corinna Vinschen wrote:
Hi folks,
I've just uploaded a new snapshot 2012-02-27 12:04:23 UTC. It
contains two code snippets which are supposed to help diagnosing BLODA
problems.
Very cool. Thanks Corinna!
--
Larry
On 2/27/2012 4:26 AM, Corinna Vinschen wrote:
Of course this is not foolproof. The only filtered system DLLs so
far are kernel32.dll, ntdll.dll, mswsock.dll, amd ws2_32.dll. If you
playing around with this, and if you find that a core system DLL is
reported (like, say, advapi32.dll),
On 2/27/2012 6:53 PM, David Rothenberger wrote:
On 2/27/2012 4:26 AM, Corinna Vinschen wrote:
Of course this is not foolproof. The only filtered system DLLs so
far are kernel32.dll, ntdll.dll, mswsock.dll, amd ws2_32.dll. If you
playing around with this, and if you find that a core
24 matches
Mail list logo
