public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DGStevens <deansx@gmail.com>
To: cygwin@cygwin.com
Subject: gdb 7.8 consistently fails to run executable - error is "dll path too long"
Date: Thu, 21 Aug 2014 00:16:00 -0000	[thread overview]
Message-ID: <1408580171694-110722.post@n5.nabble.com> (raw)

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.

I know that I must be doing something stupid, but it's escaping me.  The
only forum discussion that I could find suggested using mintty, which I am. 
I did see mention of a known bug in gdb, but no suggested workarounds, other
than running in mintty.

The following test case is the simplest that I could manage.  I see the same
failure with both 'C' and C++ files (gcc and g++, respectively).

I'm running Win7, with the old 32-bit cygwin.  cygcheck.txt should be
attached.

$> cat gdbtst.c
#include <stdio.h>

int main(int argc, char *argv[]) {
  printf("Hello World!\n");
}

$> gcc --version
gcc (GCC) 4.8.3
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$> gcc -g gdbtst.c -o gdbtst.exe
$> gdbtst.exe
Hello World!
$> gdb gdbtst.exe
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gdbtst.exe...done.
(gdb) break main
Breakpoint 1 at 0x4011be: file gdbtst.c, line 4.
(gdb) step
The program is not being run.
(gdb) run
Starting program: /home/Deans/SBX/Samples/gdbtst.exe
[New Thread 34472.0x8ad8]
dll path too long
(gdb) step
Cannot execute this command while the selected thread is running.
(gdb) quit
A debugging session is active.

        Inferior 1 [process 34472] will be killed.

Quit anyway? (y or n) y
$> cygcheck -s -v -r >cygcheck.txt

cygcheck.txt <http://cygwin.1069669.n5.nabble.com/file/n110722/cygcheck.txt>  



--
View this message in context: http://cygwin.1069669.n5.nabble.com/gdb-7-8-consistently-fails-to-run-executable-error-is-dll-path-too-long-tp110722.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
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  0:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  0:16 DGStevens [this message]
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
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=1408580171694-110722.post@n5.nabble.com \
    --to=deansx@gmail.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).