From: Luis Machado <lgustavo@codesourcery.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: mingw-w64's GDB 64-bit/32-bit debugging
Date: Tue, 06 Dec 2016 02:37:00 -0000 [thread overview]
Message-ID: <6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com> (raw)
Hi,
The configure files don't tell much other than the difference between
hosts (mingw/mingw64).
Is a native mingw-w64 gdb capable of debugging 64-bit and 32-bit Windows
processes or do we need a 32-bit gdb for a 32-bit process and a 64-bit
gdb for a 64-bit process?
Doing some tests i noticed ming-w64's 64-bit GDB doesn't quite like the
32-bit executable, choking on some 64-bit Windows symbol files and
eventually getting an unexpected signal.
---
[New Thread 9536.0x2358]
Error while mapping shared library sections:
`C:\Windows\SYSTEM32\ntdll.dll': not in executable format: File format
not recognized
Error while mapping shared library sections:
`C:\Windows\system32\wow64.dll': not in executable format: File format
not recognized
Error while mapping shared library sections:
`C:\Windows\system32\wow64win.dll': not in executable format: File
format not recognized
warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for WOW64_IMAGE_SECTION.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for NOT_AN_IMAGE.
Do you need "set solib-search-path" or "set sysroot"?
warning: Could not load shared library symbols for NOT_AN_IMAGE.
Do you need "set solib-search-path" or "set sysroot"?
Error while mapping shared library sections:
`C:\Windows\system32\wow64cpu.dll': not in executable format: File
format not recognized
[New Thread 9536.0x2740]
gdb: unknown target exception 0x4000001f at 0x401633
Thread 1 received signal ?, Unknown signal.
0x0009e0d8 in ?? ()
(gdb) info shared
From To Syms Read Shared Object Library
No C:\Windows\SYSTEM32\ntdll.dll
No C:\Windows\system32\wow64.dll
No C:\Windows\system32\wow64win.dll
No C:\Windows\system32\wow64cpu.dll
0x75080000 0x751546b4 Yes (*) C:\Windows\SysWOW64\kernel32.dll
0x74be1000 0x74d55bac Yes (*) C:\Windows\SysWOW64\KernelBase.dll
0x742f1000 0x743ad7d8 Yes (*) C:\Windows\SysWOW64\msvcrt.dll
(*): Shared library is missing debugging information.
next reply other threads:[~2016-12-06 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:37 Luis Machado [this message]
2016-12-06 3:34 ` Eli Zaretskii
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=6b0e1474-b965-ef37-bd0f-3b38aad07810@codesourcery.com \
--to=lgustavo@codesourcery.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