From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gdb 7.8 consistently fails to run executable - error is
Date: Wed, 08 Oct 2014 12:12:00 -0000 [thread overview]
Message-ID: <20141008121224.GB29235@calimero.vinschen.de> (raw)
In-Reply-To: <54294CED.9050602@onespin-solutions.com>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
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 DLL.
Thanks for looking into this. While this occurs in Cygwin-specific
code, the problem is a result of the restriction of so_list::so_name
being always SO_NAME_MAX_PATH_SIZE in length.
I'm not sure how to fix this problem yet. I'll look into it when I
had a chance to catch up with my insane mail backlog.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-08 12:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 0:16 gdb 7.8 consistently fails to run executable - error is "dll path too long" DGStevens
2014-08-21 8:02 ` gdb 7.8 consistently fails to run executable - error is Achim Gratz
2014-08-22 18:32 ` DGStevens
2014-09-25 12:19 ` Dominik Straßer
2014-09-29 14:18 ` Dominik Straßer
2014-10-08 12:12 ` Corinna Vinschen [this message]
2014-10-08 12:38 ` Dominik Straßer
2015-11-23 14:44 ` Tim Chick
2016-01-12 13:58 ` Vanda Vodkamilkevich
2016-01-12 17:30 ` Corinna Vinschen
2015-11-23 15:09 ` Tim Chick
2016-01-14 15:53 ` Jon Turney
2016-01-14 19:48 ` Tim Chick
2016-01-14 20:20 ` Jon Turney
2016-01-21 15:01 ` Tim Chick
2016-01-27 21:47 ` Jon Turney
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=20141008121224.GB29235@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).