Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: snapshot issues with mingw-w64 based targets
Date: Mon, 25 Jan 2010 19:11:00 -0000	[thread overview]
Message-ID: <2bf229d31001251110q2d2f76e1p44d64f1553b18849@mail.gmail.com> (raw)

Hi All,

I'm able to build the 20100125 snapshot using i686-w64-mingw32 no
problem, but when debugging I don't see anything beyond addresses:

$ gdb --args tst.exe
GNU gdb (GDB) 7.0.50.20100123
Copyright (C) 2010 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-w64-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from C:\cygwin\usr\src\gdb\test/tst.exe...done.
(gdb) r
Starting program: C:\cygwin\usr\src\gdb\test/tst.exe
[New Thread 1576.0x17d8]

Program received signal SIGSEGV, Segmentation fault.
0x004013da in main ()
(gdb) bt
#0  0x004013da in main ()
(gdb)

I configured it with:

CFLAGS="-I/usr/src/gdb/expat-w32/include -static
-L/usr/src/gdb/expat-w32/lib" ../gdb-7.0.1/configure
--host=i686-w64-mingw32 --target=i686-w64-mingw32
--build=i386-pc-cygwin

and build with the standard make / make install-gdb, which I used when
compiling 7.0.1 and it seems to work as expected.  Have I missed
something?

Chris

-- 
Chris Sutcliffe
http://emergedesktop.org


             reply	other threads:[~2010-01-25 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 19:11 Chris Sutcliffe [this message]
2010-01-25 20:06 ` Chris Sutcliffe

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=2bf229d31001251110q2d2f76e1p44d64f1553b18849@mail.gmail.com \
    --to=ir0nh34d@gmail.com \
    --cc=gdb@sourceware.org \
    /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