public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: matthew patton <pattonme@yahoo.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>,
	 marco atzeri <marco.atzeri@gmail.com>
Subject: Re: Cygwin GDB won't start or hangs at startup
Date: Mon, 8 Feb 2021 15:33:35 +0000 (UTC)	[thread overview]
Message-ID: <2078419709.2650216.1612798415176@mail.yahoo.com> (raw)
In-Reply-To: <CAB8Xom9QupMhxVOjd_sZYapSJScB7sQ+u=PGrX-BYUiG5f8N_w@mail.gmail.com>

On Sun, Feb 7, 2021 at 4:13 PM Jon Turney  wrote:

>> 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?).

> the lack of a backup solution is clearly an upstream bug.
> I assume iconv is usually present and only on border case the bug
> is evident.

Indeed it is.iconv is provided by glibc-common on Linux distros so it's always available. Forcing a cygwin package dependency on iconv would be easiest fix. And open an ERRATA with upstream to gracefully handle lack of the binary.  

  reply	other threads:[~2021-02-08 15:33 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
2021-02-08 13:46           ` marco atzeri
2021-02-08 15:33             ` matthew patton [this message]
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=2078419709.2650216.1612798415176@mail.yahoo.com \
    --to=pattonme@yahoo.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.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).