From: John Gilmore <gnu@toad.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: eliz@gnu.org, gdb@sourceware.org
Subject: Re: Calling __stdcall functions in the inferior
Date: Fri, 12 Oct 2012 10:20:00 -0000 [thread overview]
Message-ID: <201210121020.q9CAKMk7022512@new.toad.com> (raw)
In-Reply-To: <201210120953.q9C9rqfu020865@glazunov.sibelius.xs4all.nl>
> > Is there a way to call __stdcall functions in the inferior from GDB,
> > while debugging a C program? The case in point is GetLastError, but
> > any other function from the Windows API has this problem.
If you just need this capability to debug a particular problem, add a
dummy debugging function to the source code of your buggy program,
which has the normal calling sequence, and which just calls
GetLastError and returns its result. Then call *that* function from
GDB.
John
next prev parent reply other threads:[~2012-10-12 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 6:50 Eli Zaretskii
2012-10-12 9:54 ` Mark Kettenis
2012-10-12 10:20 ` John Gilmore [this message]
2012-10-12 10:44 ` Eli Zaretskii
2012-10-12 10:42 ` Eli Zaretskii
2012-10-12 11:28 ` Pedro Alves
2012-10-12 13:26 ` Eli Zaretskii
2012-10-15 13:17 ` Pierre Muller
2012-10-12 11:45 ` Mark Kettenis
2012-10-12 13:25 ` 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=201210121020.q9CAKMk7022512@new.toad.com \
--to=gnu@toad.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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