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 13:25:00 -0000	[thread overview]
Message-ID: <83zk3r7rg8.fsf@gnu.org> (raw)
In-Reply-To: <201210121144.q9CBinFb005271@glazunov.sibelius.xs4all.nl>

> Date: Fri, 12 Oct 2012 13:44:49 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: gdb@sourceware.org
> 
> The way call dummies work, the fact that the callee pops the stack
> shouldn't be an issue.

Then what could be the reason that

  (gdb) p GetLastError ()

crashes?  Here's what get:

  (gdb) p GetLastError()

  Program received signal SIGSEGV, Segmentation fault.
  0x7c809163 in KERNEL32!InitializeSListHead ()
     from C:\WINDOWS\system32\kernel32.dll
  The program being debugged was signaled while in a function called from GDB.
  GDB remains in the frame where the signal was received.
  To change this behavior use "set unwindonsignal on".
  Evaluation of the expression containing the function
  (KERNEL32!GetLastError) will be abandoned.
  When the function is done executing, GDB will silently stop.


      reply	other threads:[~2012-10-12 13:25 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
2012-10-12 13:25       ` Eli Zaretskii [this message]

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=83zk3r7rg8.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