public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: gdb 7.8 consistently fails to run executable - error is
Date: Thu, 21 Aug 2014 08:02:00 -0000	[thread overview]
Message-ID: <loom.20140821T100019-590@post.gmane.org> (raw)
In-Reply-To: <1408580171694-110722.post@n5.nabble.com>

DGStevens <deansx <at> gmail.com> writes:
> I'm unable to use gdb on any c/c++ executables.  When I try, gdb issues the
> message "dll path too long" and fails to start the target executable.

Try cutting your PATH after the third component.  If that helps, you could
set CYGWIN_NOWINPATH either as a system or user variable from Windows and
have that done automatically (if you use sh/bash).


Regards,
Achim.


--
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

  reply	other threads:[~2014-08-21  8:02 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 ` Achim Gratz [this message]
2014-08-22 18:32   ` gdb 7.8 consistently fails to run executable - error is 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
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=loom.20140821T100019-590@post.gmane.org \
    --to=stromeko@nexgo.de \
    --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).