Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: Calling __stdcall functions in the inferior
Date: Fri, 12 Oct 2012 10:42:00 -0000	[thread overview]
Message-ID: <834nm07z0s.fsf@gnu.org> (raw)
In-Reply-To: <201210120953.q9C9rqfu020865@glazunov.sibelius.xs4all.nl>

> 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...

> I'm not familliar with the Windows world (and don't really have a
> desire to become familliar).  But I assume "normal" (non-__stdcall)
> functions use the System V calling conventions?

Yes, it's the normal cdecl calling convention.

> * You'll need to figure out a way to distinguish __stdcall functions
>   from "normal" functions.

Does someone know where GCC stashes this info?  "ptype" doesn't reveal
this detail, AFAICS.

Thanks.


  parent reply	other threads:[~2012-10-12 10:42 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 [this message]
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=834nm07z0s.fsf@gnu.org \
    --to=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