gdb not working

gdb not working

[Lemke, Michael SF/HZA-ZIC2]

I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
However, gdb does not produce any output.

Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
Any ideas why?

pc> gdb -v
GNU gdb (GDB) Cygwin 7.9.1-1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

Install gdb 7.10.1-1
 pc> gdb -v
GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

Install gdb 7.12.1-2
 pc> gdb -v
Install gdb 8.0.1-1
 pc> gdb -v
 pc> cygcheck -c gdb
Cygwin Package Information
Package              Version        Status
gdb                  8.0.1-1        OK
 pc> uname -a
CYGWIN_NT-10.0 pc 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin

Re: gdb not working

[Marco Atzeri]

On 15.01.2021 13:28, Lemke, Michael SF/HZA-ZIC2 wrote:
> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
> However, gdb does not produce any output.
> 
> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
> Any ideas why? 

> Problem reports:      https://cygwin.com/problems.html

please provide the cygcheck.out as attachment.

Both the current and the test versions work on my installations

$ gdb -v
GNU gdb (GDB) (Cygwin 10.1-1) 10.1
..

$ gdb --version
GNU gdb (GDB) (Cygwin 9.2-1) 9.2
..

Re: gdb not working

[Jon Turney]

On 15/01/2021 12:28, Lemke, Michael SF/HZA-ZIC2 wrote:
> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
> However, gdb does not produce any output.
> 
> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
> Any ideas why?
[...]

> Install gdb 7.12.1-2
>   pc> gdb -v
> Install gdb 8.0.1-1
>   pc> gdb -v
>   pc> cygcheck -c gdb
> Cygwin Package Information
> Package              Version        Status
> gdb                  8.0.1-1        OK

You might try 'strace gdb' and see if that sheds any light on what's 
failing.

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>On 15/01/2021 12:28, Lemke, Michael wrote:
>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>> However, gdb does not produce any output.
>> 
>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
>> Any ideas why?
>[...]
>
>> Install gdb 7.12.1-2
>>   pc> gdb -v
>> Install gdb 8.0.1-1
>>   pc> gdb -v
>>   pc> cygcheck -c gdb
>> Cygwin Package Information
>> Package              Version        Status
>> gdb                  8.0.1-1        OK
>
>You might try 'strace gdb' and see if that sheds any light on what's 
>failing.

I tried that but I couldn't see anything strange. Also ldd `which gdb` is
fine.

I tried the cygcheck Marco Atzeri suggested. I am not comfortable to send
the result to the list but I checked it.

As a result I cleaned up my path to just /bin which removed some duplicate
entries in cygcheck.out but gdb still doesn't work.

The only strange part I see in cygcheck.out is a slight mess up with my
installation, a result of my moving /c/cygwin64 to /c/mystuff/ncygwin64
after my first run of setup.exe, see below.  So what has changed between 
gdb 7.10.1-1 and gdb 7.12.1-2? 

Excerpt from cygcheck.out:

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
  d5bac59bf2204d69 = '\??\C:\MyStuff\NCygwin64'
  c0a8879476f177eb = '\??\C:\MyStuff\NCygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
  d5bac59bf2204d69 = '\??\C:\MyStuff\NCygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\MyStuff\NCygwin64'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64 (ORPHANED)
  System: Key: d5bac59bf2204d69 Path: C:\MyStuff\NCygwin64
  User:   Key: e022582115c10879 Path: C:\cygwin64 (ORPHANED)
  User:   Key: d5bac59bf2204d69 Path: C:\MyStuff\NCygwin64
  User:   Key: c0a8879476f177eb Path: C:\MyStuff\NCygwin

c:  hd  NTFS    486732Mb  27% CP CS UN PA FC    QU  Windows
u:  net NTFS   4300668Mb  91% CP CS UN PA FC    QU  USERS-10

C:\MyStuff\NCygwin\home   /home     user    binary
C:\MyStuff\NCygwin64      /         system  binary,auto
C:\MyStuff\NCygwin64\bin  /usr/bin  system  binary,auto
C:\MyStuff\NCygwin64\lib  /usr/lib  system  binary,auto
cygdrive prefix           /         user    binary,posix=0,auto

Found: C:\MyStuff\NCygwin64\bin\awk
 -> C:\MyStuff\NCygwin64\bin\gawk.exe
Found: C:\MyStuff\NCygwin64\bin\bash.exe
Found: C:\MyStuff\NCygwin64\bin\cat.exe
Not Found: certutil
Not Found: clinfo
Not Found: comp
Found: C:\MyStuff\NCygwin64\bin\convert
 -> C:\MyStuff\NCygwin64\bin\magick.exe
Found: C:\MyStuff\NCygwin64\bin\cp.exe
Found: C:\MyStuff\NCygwin64\bin\cpp.exe
Not Found: crontab
Found: C:\MyStuff\NCygwin64\bin\curl.exe
Found: C:\MyStuff\NCygwin64\bin\expand.exe
Found: C:\MyStuff\NCygwin64\bin\find.exe
Found: C:\MyStuff\NCygwin64\bin\ftp.exe
Found: C:\MyStuff\NCygwin64\bin\gcc.exe
Found: C:\MyStuff\NCygwin64\bin\gdb.exe
Found: C:\MyStuff\NCygwin64\bin\grep.exe
Found: C:\MyStuff\NCygwin64\bin\hostname.exe
Found: C:\MyStuff\NCygwin64\bin\kill.exe
Not Found: klist
Found: C:\MyStuff\NCygwin64\bin\ld.exe
Found: C:\MyStuff\NCygwin64\bin\ls.exe
Found: C:\MyStuff\NCygwin64\bin\make.exe
Found: C:\MyStuff\NCygwin64\bin\mv.exe
Not Found: nslookup
Not Found: patch
Found: C:\MyStuff\NCygwin64\bin\perl.exe
Not Found: replace
Found: C:\MyStuff\NCygwin64\bin\rm.exe
Found: C:\MyStuff\NCygwin64\bin\sed.exe
Found: C:\MyStuff\NCygwin64\bin\sh.exe
Not Found: shutdown
Found: C:\MyStuff\NCygwin64\bin\sort.exe
Found: C:\MyStuff\NCygwin64\bin\ssh.exe
Found: C:\MyStuff\NCygwin64\bin\tar.exe
Found: C:\MyStuff\NCygwin64\bin\test.exe
Found: C:\MyStuff\NCygwin64\bin\timeout.exe
Found: C:\MyStuff\NCygwin64\bin\vi.exe
Found: C:\MyStuff\NCygwin64\bin\vim.exe
Found: C:\MyStuff\NCygwin64\bin\whoami.exe

Re: gdb not working

[Ken Brown]

On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>> However, gdb does not produce any output.
>>>
>>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
>>> Any ideas why?
>> [...]
>>
>>> Install gdb 7.12.1-2
>>>    pc> gdb -v
>>> Install gdb 8.0.1-1
>>>    pc> gdb -v
>>>    pc> cygcheck -c gdb
>>> Cygwin Package Information
>>> Package              Version        Status
>>> gdb                  8.0.1-1        OK
>>
>> You might try 'strace gdb' and see if that sheds any light on what's
>> failing.
> 
> I tried that but I couldn't see anything strange.

No error code?  Please show the output.

> Also ldd `which gdb` is
> fine.

Please show the output.

> I tried the cygcheck Marco Atzeri suggested. I am not comfortable to send
> the result to the list but I checked it.

Can you remove the sensitive parts and then send it?  It's hard for anyone on 
the list to help you if you don't provide information about your installation.

> As a result I cleaned up my path to just /bin which removed some duplicate
> entries in cygcheck.out but gdb still doesn't work.
> 
> The only strange part I see in cygcheck.out is a slight mess up with my
> installation, a result of my moving /c/cygwin64 to /c/mystuff/ncygwin64
> after my first run of setup.exe, see below.  So what has changed between
> gdb 7.10.1-1 and gdb 7.12.1-2?

Dependencies may have changed.  Have you checked that you have all dependencies 
of whatever version you're trying to run?  Just re-running setup should take 
care of that if that's the problem.

Ken

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>> However, gdb does not produce any output.
>>>>
>>>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
>>>> Any ideas why?
>>> [...]
>>>
>>>> Install gdb 7.12.1-2
>>>>    pc> gdb -v
>>>> Install gdb 8.0.1-1
>>>>    pc> gdb -v
>>>>    pc> cygcheck -c gdb
>>>> Cygwin Package Information
>>>> Package              Version        Status
>>>> gdb                  8.0.1-1        OK
>>>
>>> You might try 'strace gdb' and see if that sheds any light on what's
>>> failing.
>> 
>> I tried that but I couldn't see anything strange.
>
>No error code?  Please show the output.

 pc> gdb -v
 pc> echo $?
0

>
>> Also ldd `which gdb` is
>> fine.
>
>Please show the output.

pc> ldd `which gdb`
        ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fffde2c0000)
        KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fffdce40000)
        KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fffdb570000)
        cygexpat-1.dll => /usr/bin/cygexpat-1.dll (0x3fe900000)
        cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3fc1b0000)
        cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3fe770000)
        cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)
        cygmpfr-6.dll => /usr/bin/cygmpfr-6.dll (0x3f9db0000)
        cyglzma-5.dll => /usr/bin/cyglzma-5.dll (0x3fa160000)
        libpython3.6m.dll => /usr/bin/libpython3.6m.dll (0x3f78d0000)
        cygncursesw-10.dll => /usr/bin/cygncursesw-10.dll (0x3fbd70000)
        cygreadline7.dll => /usr/bin/cygreadline7.dll (0x3f90d0000)
        cygz.dll => /usr/bin/cygz.dll (0x3f7e10000)
        cygsource-highlight-4.dll => /usr/bin/cygsource-highlight-4.dll (0x3f8c70000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
        cyggmp-10.dll => /usr/bin/cyggmp-10.dll (0x3fd8e0000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
        cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
        cygboost_regex-1_66.dll => /usr/bin/cygboost_regex-1_66.dll (0x3ff520000)
        cygicui18n61.dll => /usr/bin/cygicui18n61.dll (0x3fc3e0000)
        cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
        cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
        cygicudata61.dll => /usr/bin/cygicudata61.dll (0x3fa3c0000)

>
>> I tried the cygcheck Marco Atzeri suggested. I am not comfortable to send
>> the result to the list but I checked it.
>
>Can you remove the sensitive parts and then send it?  It's hard for anyone on 
>the list to help you if you don't provide information about your installation.

I'll see what I can do.

>
>> As a result I cleaned up my path to just /bin which removed some duplicate
>> entries in cygcheck.out but gdb still doesn't work.
>> 
>> The only strange part I see in cygcheck.out is a slight mess up with my
>> installation, a result of my moving /c/cygwin64 to /c/mystuff/ncygwin64
>> after my first run of setup.exe, see below.  So what has changed between
>> gdb 7.10.1-1 and gdb 7.12.1-2?
>
>Dependencies may have changed.  Have you checked that you have all dependencies 
>of whatever version you're trying to run?  Just re-running setup should take 
>care of that if that's the problem.

I've always installed every version with setup so the dependencies should have
been taken care of. And

 pc> cygcheck -c gdb
Cygwin Package Information
Package              Version        Status
gdb                  9.2-1          OK

And one more:
 pc> gdb -v >& blah
 pc> cat blah
 pc>

i.e. empty file blah.

Re: gdb not working

[Marco Atzeri]

On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>> However, gdb does not produce any output.
>>>>>
> 
>>
>>> Also ldd `which gdb` is
>>> fine.
>>
>> Please show the output.
> 
> pc> ldd `which gdb`

>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)

>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
                                                this is very low ^^^^
>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)

>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)


I do not see duplicate entries on my system. it seems a BLODA
is interfering with dll's loading

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
>On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>>> However, gdb does not produce any output.
>>>>>>
>> 
>>>
>>>> Also ldd `which gdb` is
>>>> fine.
>>>
>>> Please show the output.
>> 
>> pc> ldd `which gdb`
>
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
>
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>                                                this is very low ^^^^
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
>
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
>
>
>I do not see duplicate entries on my system. it seems a BLODA
>is interfering with dll's loading
>

It might very well be. I also noticed the output of ldd is not reproducible.
It shows different duplicate entries when run repeatedly and the load 
address you marked is also a duplicate:

 pc> ldd `which gdb`|grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0xa0000)

Hm, is gdb dependent on gcc? I just noticed my gcc is apparently broken:
 pc> cygcheck -c gcc
Cygwin Package Information
Package              Version        Status
 pc>

Other than going through the published BLODA list is there a way I could
test and find out what is interfering? I ask because we have a lot of 
stuff installed for teleworking, especially on the network side.

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Monday, January 18, 2021 2:54 PM Lemke, Michael SF/HZA-ZIC2 wrote:
>On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
>On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>>> However, gdb does not produce any output.
>>>>>>
>> 
>>>
>>>> Also ldd `which gdb` is
>>>> fine.
>>>
>>> Please show the output.
>> 
>> pc> ldd `which gdb`
>
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
>
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>                                                this is very low ^^^^
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
>
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
>
>
>I do not see duplicate entries on my system. it seems a BLODA
>is interfering with dll's loading
>

It might very well be. I also noticed the output of ldd is not reproducible.
It shows different duplicate entries when run repeatedly and the load 
address you marked is also a duplicate:

 pc> ldd `which gdb`|grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
 pc> ldd `which gdb` | grep --color gcc
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
        cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0xa0000)

Hm, is gdb dependent on gcc? I just noticed my gcc is apparently broken:
 pc> cygcheck -c gcc
Cygwin Package Information
Package              Version        Status
 pc>


P.S.:
 pc> cygcheck -c gcc
Cygwin Package Information
Package              Version        Status
 pc> gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/10/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: /mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0/configure --srcdir=/mnt/share/cygpkgs/gcc/gcc.x86_64/src/gcc-10.2.0 --prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc --docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C --build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin --without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib --with-gcc-major-version-only --enable-shared --enable-shared-libgcc --enable-static --enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit --with-dwarf2 --with-tune=generic --enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-graphite --enable-threads=posix --enable-libatomic --enable-libgomp --enable-libquadmath --enable-libquadmath-support --disable-libssp --enable-libada --disable-symvers --with-gnu-ld --with-gnu-as --with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix --without-libintl-prefix --with-system-zlib --enable-linker-build-id --with-default-libstdcxx-abi=gcc4-compatible --enable-libstdcxx-filesystem-ts
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.0 (GCC)

And I can compile C programs.

Re: gdb not working

[Ken Brown]

On 1/18/2021 8:54 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
> On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
>> On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
>>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>>>> However, gdb does not produce any output.
>>>>>>>
>>>
>>>>
>>>>> Also ldd `which gdb` is
>>>>> fine.
>>>>
>>>> Please show the output.
>>>
>>> pc> ldd `which gdb`
>>
>>>           cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>>>           cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
>>
>>>           cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>>                                                 this is very low ^^^^
>>>           cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
>>
>>>           cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>>>           cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
>>
>>
>> I do not see duplicate entries on my system. it seems a BLODA
>> is interfering with dll's loading
>>
> 
> It might very well be. I also noticed the output of ldd is not reproducible.
> It shows different duplicate entries when run repeatedly and the load
> address you marked is also a duplicate:
> 
>   pc> ldd `which gdb`|grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>   pc> ldd `which gdb` | grep --color gcc
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0xa0000)
> 
> Hm, is gdb dependent on gcc? I just noticed my gcc is apparently broken:
>   pc> cygcheck -c gcc
> Cygwin Package Information
> Package              Version        Status

The package containing gcc is called "gcc-core", not "gcc":

$ cygcheck -f /usr/bin/gcc.exe
gcc-core-10.2.0-1

$ cygcheck -c gcc-core
Cygwin Package Information
Package              Version        Status
gcc-core             10.2.0-1       OK

> Other than going through the published BLODA list is there a way I could
> test and find out what is interfering? I ask because we have a lot of
> stuff installed for teleworking, especially on the network side.

You can sometimes catch BLODA by running strace.  It may show some DLL being 
loaded that shouldn't be, typically from security software.

Ken

Re: gdb not working

[Ken Brown]

[Resending.  Accidentally sent to OP instead of list.]

On 1/18/2021 8:08 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>> However, gdb does not produce any output.
>>>>>
>>>>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
>>>>> Any ideas why?
>>>> [...]
>>>>
>>>>> Install gdb 7.12.1-2
>>>>>     pc> gdb -v
>>>>> Install gdb 8.0.1-1
>>>>>     pc> gdb -v
>>>>>     pc> cygcheck -c gdb
>>>>> Cygwin Package Information
>>>>> Package              Version        Status
>>>>> gdb                  8.0.1-1        OK
>>>>
>>>> You might try 'strace gdb' and see if that sheds any light on what's
>>>> failing.
>>>
>>> I tried that but I couldn't see anything strange.
>>
>> No error code?  Please show the output.
> 
>   pc> gdb -v
>   pc> echo $?
> 0

I was asking for the strace output.  It might just show the same DLL loading 
issues that Marco noticed, or it might show something more.

>>
>>> Also ldd `which gdb` is
>>> fine.
>>
>> Please show the output.
> 
> pc> ldd `which gdb`
>          ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fffde2c0000)
>          KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fffdce40000)
>          KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fffdb570000)
>          cygexpat-1.dll => /usr/bin/cygexpat-1.dll (0x3fe900000)
>          cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3fc1b0000)
>          cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3fe770000)
>          cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)
>          cygmpfr-6.dll => /usr/bin/cygmpfr-6.dll (0x3f9db0000)
>          cyglzma-5.dll => /usr/bin/cyglzma-5.dll (0x3fa160000)
>          libpython3.6m.dll => /usr/bin/libpython3.6m.dll (0x3f78d0000)
>          cygncursesw-10.dll => /usr/bin/cygncursesw-10.dll (0x3fbd70000)
>          cygreadline7.dll => /usr/bin/cygreadline7.dll (0x3f90d0000)
>          cygz.dll => /usr/bin/cygz.dll (0x3f7e10000)
>          cygsource-highlight-4.dll => /usr/bin/cygsource-highlight-4.dll (0x3f8c70000)
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
>          cyggmp-10.dll => /usr/bin/cyggmp-10.dll (0x3fd8e0000)
>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
>          cygboost_regex-1_66.dll => /usr/bin/cygboost_regex-1_66.dll (0x3ff520000)
>          cygicui18n61.dll => /usr/bin/cygicui18n61.dll (0x3fc3e0000)
>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
>          cygicudata61.dll => /usr/bin/cygicudata61.dll (0x3fa3c0000)
> 
>>
>>> I tried the cygcheck Marco Atzeri suggested. I am not comfortable to send
>>> the result to the list but I checked it.
>>
>> Can you remove the sensitive parts and then send it?  It's hard for anyone on
>> the list to help you if you don't provide information about your installation.
> 
> I'll see what I can do.
> 
>>
>>> As a result I cleaned up my path to just /bin which removed some duplicate
>>> entries in cygcheck.out but gdb still doesn't work.
>>>
>>> The only strange part I see in cygcheck.out is a slight mess up with my
>>> installation, a result of my moving /c/cygwin64 to /c/mystuff/ncygwin64
>>> after my first run of setup.exe, see below.  So what has changed between
>>> gdb 7.10.1-1 and gdb 7.12.1-2?
>>
>> Dependencies may have changed.  Have you checked that you have all dependencies
>> of whatever version you're trying to run?  Just re-running setup should take
>> care of that if that's the problem.
> 
> I've always installed every version with setup so the dependencies should have
> been taken care of. And
> 
>   pc> cygcheck -c gdb
> Cygwin Package Information
> Package              Version        Status
> gdb                  9.2-1          OK

cygcheck doesn't check dependencies.  But that doesn't appear to be the issue 
anyway.

Ken

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
>
>[Resending.  Accidentally sent to OP instead of list.]

{Happens here too. Reply All or Reply (in Outlook) both send to OP instead of list.]

>
>On 1/18/2021 8:08 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>>>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>>>> On 15/01/2021 12:28, Lemke, Michael wrote:
>>>>>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>>>>>> However, gdb does not produce any output.
>>>>>>
>>>>>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
>>>>>> Any ideas why?
>>>>> [...]
>>>>>
>>>>>> Install gdb 7.12.1-2
>>>>>>     pc> gdb -v
>>>>>> Install gdb 8.0.1-1
>>>>>>     pc> gdb -v
>>>>>>     pc> cygcheck -c gdb
>>>>>> Cygwin Package Information
>>>>>> Package              Version        Status
>>>>>> gdb                  8.0.1-1        OK
>>>>>
>>>>> You might try 'strace gdb' and see if that sheds any light on what's
>>>>> failing.
>>>>
>>>> I tried that but I couldn't see anything strange.
>>>
>>> No error code?  Please show the output.
>> 
>>   pc> gdb -v
>>   pc> echo $?
>> 0
>
>I was asking for the strace output.  It might just show the same DLL loading 
>issues that Marco noticed, or it might show something more.
>

Ok, here are the first 100 lines, the whole thing is over 2MB. To me this
looks strange already (cygstdc++-6.dll).

--- Process 32204 created
--- Process 32204 loaded C:\Windows\System32\ntdll.dll at 00007fffde2c0000
--- Process 32204 loaded C:\Windows\System32\kernel32.dll at 00007fffdce40000
--- Process 32204 loaded C:\Windows\System32\KernelBase.dll at 00007fffdb570000
--- Process 32204 thread 13420 created
--- Process 32204 thread 32700 created
--- Process 32204 thread 25220 created
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygwin1.dll at 0000000180040000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygintl-8.dll at 00000003fbff0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygiconv-2.dll at 00000003fe770000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygncursesw-10.dll at 00000003fbd70000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygexpat-1.dll at 00000003fe900000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cyglzma-5.dll at 00000003f9e60000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygmpfr-6.dll at 00000003f9aa0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygz.dll at 00000003f7b00000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\libpython3.6m.dll at 00000003f75c0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygreadline7.dll at 00000003f8dc0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cyggcc_s-seh-1.dll at 00000003fdf60000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygsource-highlight-4.dll at 00000003f8960000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygstdc++-6.dll at 00000003f8530000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cyggmp-10.dll at 00000003fd720000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygboost_regex-1_66.dll at 00000003ff520000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygstdc++-6.dll at 00000000034d0000
--- Process 32204 unloaded DLL at 00000000034d0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygicui18n61.dll at 00000003fc220000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygicuuc61.dll at 00000003fc080000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygicudata61.dll at 00000003fa3c0000
--- Process 32204 loaded C:\MyStuff\NCygwin64\bin\cygicuuc61.dll at 00000000034d0000
--- Process 32204 unloaded DLL at 00000000034d0000
    3       3 [main] gdb (32204) **********************************************
  654     657 [main] gdb (32204) Program name: C:\MyStuff\NCygwin64\bin\gdb.exe (windows pid 32204)
  180     837 [main] gdb (32204) OS version:   Windows NT-10.0
  141     978 [main] gdb (32204) **********************************************
--- Process 32204 loaded C:\Windows\System32\advapi32.dll at 00007fffdd700000
--- Process 32204 loaded C:\Windows\System32\msvcrt.dll at 00007fffdc5a0000
--- Process 32204 loaded C:\Windows\System32\sechost.dll at 00007fffdc6f0000
--- Process 32204 loaded C:\Windows\System32\rpcrt4.dll at 00007fffdd7b0000
--- Process 32204 loaded C:\Windows\System32\cryptbase.dll at 00007fffdab80000
--- Process 32204 loaded C:\Windows\System32\bcryptprimitives.dll at 00007fffdb350000
 5896    6874 [main] gdb (32204) sigprocmask: 0 = sigprocmask (0, 0x0, 0x180324D70)
 3918   10792 [main] gdb (32204) open_shared: name shared.5, n 5, shared 0x180030000 (wanted 0x180030000), h 0xF0, *m 6
  143   10935 [main] gdb (32204) user_heap_info::init: heap base 0x800000000, heap top 0x800000000, heap size 0x20000000 (536870912)
  182   11117 [main] gdb (32204) open_shared: name S-1-5-21-435809281-806517502-2525237208-127212.1, n 1, shared 0x180020000 (wanted 0x180020000), h 0x100, *m 6
  108   11225 [main] gdb (32204) user_info::create: opening user shared for 'S-1-5-21-<redacted>' at 0x180020000
  106   11331 [main] gdb (32204) user_info::create: user shared version AB1FCCE8
  207   11538 [main] gdb (32204) fhandler_pipe::create: name \\.\pipe\cygwin-d5bac59bf2204d69-32204-sigwait, size 11440, mode PIPE_TYPE_MESSAGE
  459   11997 [main] gdb (32204) fhandler_pipe::create: pipe read handle 0x114
  108   12105 [main] gdb (32204) fhandler_pipe::create: CreateFile: name \\.\pipe\cygwin-d5bac59bf2204d69-32204-sigwait
  378   12483 [main] gdb (32204) fhandler_pipe::create: pipe write handle 0x118
  191   12674 [main] gdb (32204) dll_crt0_0: finished dll_crt0_0 initialization
--- Process 32204 thread 32712 created
 1664   14338 [sig] gdb (32204) wait_sig: entering ReadFile loop, my_readsig 0x114, my_sendsig 0x118
--- Process 32204 loaded C:\Program Files\Common Files\McAfee\SystemCore\mfehcinj.dll at 0000000052b60000
--- Process 32204 loaded C:\Windows\System32\user32.dll at 00007fffdd4e0000
--- Process 32204 loaded C:\Windows\System32\win32u.dll at 00007fffdb440000
--- Process 32204 loaded C:\Windows\System32\gdi32.dll at 00007fffdd4b0000
--- Process 32204 loaded C:\Windows\System32\gdi32full.dll at 00007fffdbfb0000
--- Process 32204 loaded C:\Windows\System32\msvcp_win.dll at 00007fffdc180000
--- Process 32204 loaded C:\Windows\System32\ucrtbase.dll at 00007fffdb470000
--- Process 32204 loaded C:\Windows\System32\wintrust.dll at 00007fffdb3e0000
--- Process 32204 loaded C:\Windows\System32\msasn1.dll at 00007fffdb1e0000
--- Process 32204 loaded C:\Windows\System32\crypt32.dll at 00007fffdc220000
--- Process 32204 loaded C:\Windows\System32\imm32.dll at 00007fffdd950000
--- Process 32204 loaded C:\Program Files\Common Files\McAfee\SystemCore\mfehcthe.dll at 0000000052b50000
--- Process 32204 loaded C:\Program Files\McAfee\Endpoint Security\Adaptive Threat Protection\mfedeeprem64.dll at 00007fffcc700000
--- Process 32204 loaded C:\Windows\System32\ole32.dll at 00007fffdc440000
--- Process 32204 loaded C:\Windows\System32\combase.dll at 00007fffdcb00000
--- Process 32204 loaded C:\Windows\System32\oleaut32.dll at 00007fffdc370000
23527   37865 [main] gdb (32204) time: 1610988403 = time(0x0)
  201   38066 [main] gdb (32204) mount_info::conv_to_posix_path: conv_to_posix_path (C:\MyStuff\NCygwin\home\myuser\gd, 0x0, no-add-slash)
  102   38168 [main] gdb (32204) normalize_win32_path: C:\MyStuff\NCygwin\home\myuser\gd = normalize_win32_path (C:\MyStuff\NCygwin\home\myuser\gd)
   67   38235 [main] gdb (32204) mount_info::conv_to_posix_path: /home/myuser/gd = conv_to_posix_path (C:\MyStuff\NCygwin\home\myuser\gd)
   98   38333 [main] gdb (32204) sigprocmask: 0 = sigprocmask (0, 0x0, 0x800018130)
  773   39106 [main] gdb (32204) _cygwin_istext_for_stdio: fd 0: not open
  104   39210 [main] gdb (32204) _cygwin_istext_for_stdio: fd 1: not open
  107   39317 [main] gdb (32204) _cygwin_istext_for_stdio: fd 2: not open
  347   39664 [main] gdb (32204) open_shared: name cygpid.9212, n 9212, shared 0x180010000 (wanted 0x180010000), h 0x218, *m 2
  110   39774 [main] gdb (32204) time: 1610988403 = time(0x0)
  193   39967 [main] gdb 9212 pinfo::thisproc: myself dwProcessId 32204
...


>>>
>>>> Also ldd `which gdb` is
>>>> fine.
>>>
>>> Please show the output.
>> 
>> pc> ldd `which gdb`
>>          ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fffde2c0000)
>>          KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fffdce40000)
>>          KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fffdb570000)
>>          cygexpat-1.dll => /usr/bin/cygexpat-1.dll (0x3fe900000)
>>          cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3fc1b0000)
>>          cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3fe770000)
>>          cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)
>>          cygmpfr-6.dll => /usr/bin/cygmpfr-6.dll (0x3f9db0000)
>>          cyglzma-5.dll => /usr/bin/cyglzma-5.dll (0x3fa160000)
>>          libpython3.6m.dll => /usr/bin/libpython3.6m.dll (0x3f78d0000)
>>          cygncursesw-10.dll => /usr/bin/cygncursesw-10.dll (0x3fbd70000)
>>          cygreadline7.dll => /usr/bin/cygreadline7.dll (0x3f90d0000)
>>          cygz.dll => /usr/bin/cygz.dll (0x3f7e10000)
>>          cygsource-highlight-4.dll => /usr/bin/cygsource-highlight-4.dll (0x3f8c70000)
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf60000)
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3f8840000)
>>          cyggmp-10.dll => /usr/bin/cyggmp-10.dll (0x3fd8e0000)
>>          cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x170000)
>>          cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3600000)
>>          cygboost_regex-1_66.dll => /usr/bin/cygboost_regex-1_66.dll (0x3ff520000)
>>          cygicui18n61.dll => /usr/bin/cygicui18n61.dll (0x3fc3e0000)
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3fc240000)
>>          cygicuuc61.dll => /usr/bin/cygicuuc61.dll (0x3600000)
>>          cygicudata61.dll => /usr/bin/cygicudata61.dll (0x3fa3c0000)
>> 
>>>
>>>> I tried the cygcheck Marco Atzeri suggested. I am not comfortable to send
>>>> the result to the list but I checked it.
>>>
>>> Can you remove the sensitive parts and then send it?  It's hard for anyone on
>>> the list to help you if you don't provide information about your installation.
>> 
>> I'll see what I can do.
>> 
>>>
>>>> As a result I cleaned up my path to just /bin which removed some duplicate
>>>> entries in cygcheck.out but gdb still doesn't work.
>>>>
>>>> The only strange part I see in cygcheck.out is a slight mess up with my
>>>> installation, a result of my moving /c/cygwin64 to /c/mystuff/ncygwin64
>>>> after my first run of setup.exe, see below.  So what has changed between
>>>> gdb 7.10.1-1 and gdb 7.12.1-2?
>>>
>>> Dependencies may have changed.  Have you checked that you have all dependencies
>>> of whatever version you're trying to run?  Just re-running setup should take
>>> care of that if that's the problem.
>> 
>> I've always installed every version with setup so the dependencies should have
>> been taken care of.
>> 

Re: gdb not working

[Ken Brown]

On 1/18/2021 12:35 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
> On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
>> I was asking for the strace output.  It might just show the same DLL loading
>> issues that Marco noticed, or it might show something more.
>>
> 
> Ok, here are the first 100 lines, the whole thing is over 2MB. To me this
> looks strange already (cygstdc++-6.dll).
[...]
> --- Process 32204 loaded C:\Program Files\Common Files\McAfee\SystemCore\mfehcthe.dll at 0000000052b50000
> --- Process 32204 loaded C:\Program Files\McAfee\Endpoint Security\Adaptive Threat Protection\mfedeeprem64.dll at 00007fffcc700000

This could be the culprit.  Can you exclude your Cygwin directory from McAfee?

Ken

RE: gdb not working

[Lemke, Michael SF/HZA-ZIC2]

On Monday, January 18, 2021 6:42 PM Ken Brown wrote:
>On 1/18/2021 12:35 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
>>> I was asking for the strace output.  It might just show the same DLL loading
>>> issues that Marco noticed, or it might show something more.
>>>
>> 
>> Ok, here are the first 100 lines, the whole thing is over 2MB. To me this
>> looks strange already (cygstdc++-6.dll).
>[...]
>> --- Process 32204 loaded C:\Program Files\Common Files\McAfee\SystemCore\mfehcthe.dll at 0000000052b50000
>> --- Process 32204 loaded C:\Program Files\McAfee\Endpoint Security\Adaptive Threat Protection\mfedeeprem64.dll at 00007fffcc700000
>
>This could be the culprit.  Can you exclude your Cygwin directory from McAfee?

Unfortunately not. It is managed centrally. But then good to know I can't use gdb here. I feel safe now...

Thanks for all your help.

Michael