From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: Re: gdb not working
Date: Mon, 18 Jan 2021 11:52:59 -0500 [thread overview]
Message-ID: <a541f00f-7ac4-c8b7-8d1f-6d39690e072b@cornell.edu> (raw)
In-Reply-To: <VI1PR03MB64465EA77323D6609D159168BEA40@VI1PR03MB6446.eurprd03.prod.outlook.com>
[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
next prev parent reply other threads:[~2021-01-18 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 12:28 Lemke, Michael SF/HZA-ZIC2
2021-01-15 15:25 ` Marco Atzeri
2021-01-15 15:44 ` Jon Turney
2021-01-15 18:47 ` Lemke, Michael SF/HZA-ZIC2
2021-01-15 20:02 ` Ken Brown
2021-01-18 13:08 ` Lemke, Michael SF/HZA-ZIC2
2021-01-18 13:22 ` Marco Atzeri
2021-01-18 13:54 ` Lemke, Michael SF/HZA-ZIC2
2021-01-18 13:58 ` Lemke, Michael SF/HZA-ZIC2
2021-01-18 16:50 ` Ken Brown
2021-01-18 16:52 ` Ken Brown [this message]
2021-01-18 17:35 ` Lemke, Michael SF/HZA-ZIC2
2021-01-18 17:42 ` Ken Brown
2021-01-18 18:54 ` Lemke, Michael SF/HZA-ZIC2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a541f00f-7ac4-c8b7-8d1f-6d39690e072b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).