public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin GDB won't start or hangs at startup
Date: Sun, 7 Feb 2021 14:25:48 +0000	[thread overview]
Message-ID: <717b4667-fb2f-a4ef-5cdf-6092c79ab18b@dronecode.org.uk> (raw)
In-Reply-To: <b7d1da20-af6f-24b1-14db-9cef93f564c4@gmail.com>

On 05/02/2021 19:06, Marco Atzeri via Cygwin wrote:
> On 05.02.2021 17:39, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, February 5, 2021 4:18 PM Takashi Yano wrote:
>>> On Fri, 5 Feb 2021 10:07:46 +0100
>>> Marco Atzeri wrote:
>>>> On 05.02.2021 08:55, Daniel Röhrborn via Cygwin wrote:
>>>>>> On 04.02.2021 13:13, Daniel Röhrborn via Cygwin wrote:
>>>>
> 
>>>
>>> I looked into this problem and found this issue causes if iconv
>>> cannot be found in the search path.
>>>
>>> Installing libiconv package should solve the issue, I guess.
>>
>> I can confirm that installing libiconv solves the problem. So it
>> was not a case of BLODA here.
>>
>>>
>>> It seems that the GDB package should set a dependency on libiconv.
>>>
>>
>> I had libiconv2 installed. Is that somehow related?
> 
> 
> gdb always needed the shared lib in libiconv2
> 
> $ cygcheck /usr/bin/gdb.exe | grep iconv
>    D:\cygwin64\bin\cygiconv-2.dll
> 
> $ cygcheck -f /usr/bin/cygiconv-2.dll
> libiconv2-1.16-2
> 
> but is seems the last versions are also calling
> the program that is packaged separately
> 
> $ cygcheck -f /usr/bin/iconv.exe
> libiconv-1.16-2
> 
> this dependency is more difficult to catch
> and it was missed when GDB was packaged

Thanks for investigating this, and fixing it on sourceware.

I've updated the .cygport appropriately.

It seems that gdb wants to run 'iconv -l' to list the available encodings.

It looks like perhaps an upstream bug that gdb outputs nothing when 
iconv can't be found (rather than using the default encoding?).

  reply	other threads:[~2021-02-07 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  7:55 Daniel Röhrborn
2021-02-05  9:07 ` Marco Atzeri
2021-02-05 14:07   ` Lemke, Michael  SF/HZA-ZIC2
2021-02-05 14:17     ` Lemke, Michael  SF/HZA-ZIC2
2021-02-05 15:18   ` Takashi Yano
2021-02-05 16:39     ` Lemke, Michael  SF/HZA-ZIC2
2021-02-05 19:06       ` Marco Atzeri
2021-02-07 14:25         ` Jon Turney [this message]
2021-02-08 13:46           ` marco atzeri
2021-02-08 15:33             ` matthew patton
2021-02-08 17:31               ` Marco Atzeri
2021-02-05 17:00     ` Marco Atzeri
  -- strict thread matches above, loose matches on Subject: below --
2021-02-04 12:13 Daniel Röhrborn
2021-02-04 13:45 ` Lemke, Michael  SF/HZA-ZIC2
2021-02-04 14:54 ` Marco Atzeri

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=717b4667-fb2f-a4ef-5cdf-6092c79ab18b@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).