From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: Tim Chick <chick@computergeek.freeserve.co.uk>
Subject: Re: gdb 7.8 consistently fails to run executable - error is
Date: Thu, 14 Jan 2016 15:53:00 -0000 [thread overview]
Message-ID: <5697BD0E.10500@dronecode.org.uk> (raw)
In-Reply-To: <1448291381719-122912.post@n5.nabble.com>
On 23/11/2015 15:09, Tim Chick wrote:
>> Am 08.10.2014 um 14:12 schrieb Corinna Vinschen:
>>> On Sep 29 14:13, Dominik StraÃer wrote:
>>>> Hi all,
>> Hi Corinna,
>>
>>>> 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.
>>>
> <SNIP>
>>>
>>> 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.
>> I only see a chance by makin this a dynamic storage.
>> as indicated in solist.h
>
> Dear All,
>
> I experienced the same problem.
>
> The error will occur if the path of the dll is too long, OR if gdb can not
> access the dll for some reason. If the dll can not be accesed, then the call
> to realpath() fails, and you get the "dll path too long" message.
>
> In my case, the path was never too long. Making the change below lets you
> debug your applications:
Thanks very much for the patch.
I've built and uploaded a test release of gdb 7.10.1 with a tweaked
version of this patch added.
Perhaps you could try that and see if it improves things for you?
I wasn't able to reproduce the problem where realpath() fails for some
DLL, even using a non-administrator account.
Can you provide some more information about what path realpath() is
failing for, and do you have any idea why?
> --- gdb-7.9.1-1.src/gdb.i686/src/gdb-7.9.1/gdb/windows-nat.c.orig 2015-11-23
> 11:43:17.834000000 +0000
> +++ gdb-7.9.1-1.src/gdb.i686/src/gdb-7.9.1/gdb/windows-nat.c 2015-11-23
> 14:17:30.302252500 +0000
> @@ -623,7 +623,8 @@ windows_make_so (const char *name, LPVOI
> free (rname);
> }
> else
> - error (_("dll path too long"));
> + warning (_("dll path too long, or can not be accessed '\"%s\"'"),
> + name);
> }
> /* Record cygwin1.dll .text start/end. */
> p = strchr (so->so_name, '\0') - (sizeof ("/cygwin1.dll") - 1);
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-01-14 15:22 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
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 [this message]
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=5697BD0E.10500@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=chick@computergeek.freeserve.co.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).