From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: gdb@sourceware.org
Subject: Re: Calling __stdcall functions in the inferior
Date: Fri, 12 Oct 2012 11:45:00 -0000 [thread overview]
Message-ID: <201210121144.q9CBinFb005271@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <834nm07z0s.fsf@gnu.org> (message from Eli Zaretskii on Fri, 12 Oct 2012 12:41:55 +0200)
> Date: Fri, 12 Oct 2012 12:41:55 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Date: Fri, 12 Oct 2012 11:53:52 +0200 (CEST)
> > From: Mark Kettenis <mark.kettenis@xs4all.nl>
> > CC: gdb@sourceware.org
> >
> > > Date: Fri, 12 Oct 2012 08:50:02 +0200
> > > From: Eli Zaretskii <eliz@gnu.org>
> > >
> > > 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.
> >
> > Probably not. We only implement the System V and Darwin calling
> > conventions for i386.
>
> But we also support Pascal, AFAIK, which uses this convention: the
> callee pops the stack. The only difference is that the arguments are
> pushed right to left, unlike with Pascal. So I thought we already had
> this somewhere...
The way call dummies work, the fact that the callee pops the stack
shouldn't be an issue.
next prev parent reply other threads:[~2012-10-12 11:45 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
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 [this message]
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=201210121144.q9CBinFb005271@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eliz@gnu.org \
--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