public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Terry Cross <tcross77@hotmail.com>
To: cygwin@cygwin.com
Subject: DBG Having internal problems on Win7
Date: Sun, 17 Nov 2013 00:01:00 -0000	[thread overview]
Message-ID: <BLU0-SMTP78B2CF505F549FF008FE3AC5E50@phx.gbl> (raw)

I am attempting to develop a program in C. Visual Studio encounters 
errors in Microsoft's own libraries with the version I am using, so that 
looks like the long path to project success.

So this is a fresh install of 64-bit Cygwin on a 64-bit Win7 platform.  
Using the Cygwin bash terminal, I have the following experience when I 
attempt to use DBG on a program I have freshly compiled with GCC:

*$ gdb a.exe
GNU gdb (GDB) 7.6.50.20130728-cvs (cygwin-special)
Copyright (C) 2013 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 "x86_64-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 /cygdrive/c/MinGW/msys/1.0/home/Mark 
DeCoursey/a.exe...done.
(gdb) b 361
Breakpoint 1 at 0x40237d: file JCPlus.c, line 361.
(gdb) r "And I say to myself, what a wonderful life."
Starting program: /cygdrive/c/MinGW/msys/1.0/home/Mark DeCoursey/a.exe 
"And I say to myself, what a wonderful life."
[New Thread 10348.0x2c24]
dll path too long
warning: `/cygdrive/c/Windows/system32/ntdll.dll': Shared library 
architecture i386:x86-64 is not compatible with target architecture i386.
warning: `/cygdrive/c/Windows/SYSTEM32/wow64.dll': Shared library 
architecture i386:x86-64 is not compatible with target architecture i386.
warning: `/cygdrive/c/Windows/SYSTEM32/wow64win.dll': Shared library 
architecture i386:x86-64 is not compatible with target architecture i386.
warning: `/cygdrive/c/Windows/SYSTEM32/wow64cpu.dll': Shared library 
architecture i386:x86-64 is not compatible with target architecture i386.
dll path too long
dll path too long
dll path too long
dll path too long
gdb: unknown target exception 0x4000001f at 0x40237d

Program received signal ?, Unknown signal.
0x0008dbf8 in ?? ()
(gdb)
*
Has anyone else experienced this problem?  Does this information offer 
any clue that I am making an error?

Thanks for any ideas.

--
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:[~2013-11-17  0:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BLU0-SMTP78B2CF505F549FF008FE3AC5E50@phx.gbl \
    --to=tcross77@hotmail.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).