From: Eli Zaretskii <eliz@gnu.org>
To: John Gilmore <gnu@toad.com>
Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org
Subject: Re: Calling __stdcall functions in the inferior
Date: Fri, 12 Oct 2012 10:44:00 -0000 [thread overview]
Message-ID: <83391k7ywt.fsf@gnu.org> (raw)
In-Reply-To: <201210121020.q9CAKMk7022512@new.toad.com>
> cc: eliz@gnu.org, gdb@sourceware.org
> Date: Fri, 12 Oct 2012 03:20:22 -0700
> From: John Gilmore <gnu@toad.com>
>
> 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.
Yes, Emacs on Windows already does that. I just thought there's a
better way, but I guess not.
Thanks.
next prev parent reply other threads:[~2012-10-12 10:44 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
2012-10-12 10:44 ` Eli Zaretskii [this message]
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=83391k7ywt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--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