On 21/01/2016 09:10, Tim Chick wrote:
Jon TURNEY wrote
On 14/01/2016 16:02, Tim Chick wrote:
Jon TURNEY wrote
I built a 32-bit version as well, but there was a slight delay with that
getting moved into the release. It should be mirroring out now, though.
Hi Jon,
I've just tried the 7.10.1
Jon TURNEY wrote
> On 14/01/2016 16:02, Tim Chick wrote:
>> Jon TURNEY wrote
>
> I built a 32-bit version as well, but there was a slight delay with that
> getting moved into the release. It should be mirroring out now, though.
Hi Jon,
I've just tried the 7.10.1-1 package, and it works fine fo
On 14/01/2016 16:02, Tim Chick wrote:
Jon TURNEY wrote
Can you provide some more information about what path realpath() is
failing for, and do you have any idea why?
The first one which fails for me is "c:\windows\system32\dgapi.dll"
I believe this is some security software installed on my ma
Jon TURNEY wrote
> Can you provide some more information about what path realpath() is
> failing for, and do you have any idea why?
The first one which fails for me is "c:\windows\system32\dgapi.dll"
I believe this is some security software installed on my machine by my
employer. I guess the sof
On 23/11/2015 15:09, Tim Chick wrote:
Am 08.10.2014 um 14:12 schrieb Corinna Vinschen:
On Sep 29 14:13, Dominik Straßer wrote:
Hi all,
Hi Corinna,
I've dug into the gdb sources. The problem is in the cygwin-only
part and is not about the PATH variable but about one single DLL
file name.
Thi
On Jan 12 13:34, Vanda Vodkamilkevich wrote:
> Hi,
>
> I'm reacting to this email with a long delay but I just wanted to let you
> know that this change saved my life, now I am finally able to debug again
> with cygwin (w7 64bits , 32 bits cygwin) because I was blocked by a nasty
> "security" dll
Hi,
I'm reacting to this email with a long delay but I just wanted to let you
know that this change saved my life, now I am finally able to debug again
with cygwin (w7 64bits , 32 bits cygwin) because I was blocked by a nasty
"security" dll (part of Arkoon Security). A big thank you...
Additional
> Am 08.10.2014 um 14:12 schrieb Corinna Vinschen:
>> On Sep 29 14:13, Dominik Straßer wrote:
>>> Hi all,
> Hi Corinna,
>
>>> I've dug into the gdb sources. The problem is in the cygwin-only
>>> part and is not about the PATH variable but about one single DLL
>>> file name.
>>>
>>> This pat
Hi Dominik,
In my case, it was not down to the string size being too small. I seemed to
suffer exactly the same problem.
You get the same error if Windows can't access the dll. This seems to happen
for some "special" dlls.
The size of any PATH variable won't matter - the path it refers to here i
Am 08.10.2014 um 14:12 schrieb Corinna Vinschen:
> On Sep 29 14:13, Dominik Straßer wrote:
>> Hi all,
Hi Corinna,
>> I've dug into the gdb sources. The problem is in the cygwin-only
>> part and is not about the PATH variable but about one single DLL
>> file name.
>>
>> This path length is *fixed
On Sep 29 14:13, Dominik Straßer wrote:
> Hi all,
> I've dug into the gdb sources.
> The problem is in the cygwin-only part and is not about the PATH
> variable but about one single DLL file name.
>
> This path length is *fixed* to 512 characters (SO_NAME_MAX_PATH_SIZE)
> for the *realpath* of the
Hi all,
I've dug into the gdb sources.
The problem is in the cygwin-only part and is not about the PATH
variable but about one single DLL file name.
This path length is *fixed* to 512 characters (SO_NAME_MAX_PATH_SIZE)
for the *realpath* of the DLL.
So there's no way for the user to work around t
Hi,
I am running into the same issue.
My path is stripped down as far as possible:
$ echo $PATH
/usr/local/bin:/usr/bin
But still no cigar.
$ gdb
/local/night/fizz_build_Win7_with_icons/libraries/compilelib/unittest/exec/cygwin64/MINGW/normal_mt_so/unittest.exe
GNU gdb (GDB) 7.8
Copyright (C) 201
Hi Achim-
Thanks. Unfortunately, the change didn't seem to help regarding my issue
with GDB. I don't know if it matters, but I fired up an old computer
running XP. I updated all of the Cygwin software, and tried the same test.
It worked fine on XP, but it seems to fail on Win7, at least for me
DGStevens gmail.com> writes:
> I'm unable to use gdb on any c/c++ executables. When I try, gdb issues the
> message "dll path too long" and fails to start the target executable.
Try cutting your PATH after the third component. If that helps, you could
set CYGWIN_NOWINPATH either as a system or
I'm unable to use gdb on any c/c++ executables. When I try, gdb issues the
message "dll path too long" and fails to start the target executable.
I know that I must be doing something stupid, but it's escaping me. The
only forum discussion that I could find suggested using mintty, which I am.
I
16 matches
Mail list logo
