Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix up msymbol type of dll trampoline to mst_solib_trampoline
Date: Fri, 05 Jul 2013 12:22:00 -0000	[thread overview]
Message-ID: <51D6BA7A.7040500@codesourcery.com> (raw)
In-Reply-To: <51D688D3.8000104@gmail.com>

On 07/05/2013 04:50 PM, asmwarrior wrote:
> This is my testing on the patch, it works fine.
> It looks like the issue only happens when __declspec(dllimport) is NOT used when building the exe file.
>

Thanks for the clarification of this issue and playing with this patch.

>
> BTW:
> 1, It looks like I can't set a breakpoint on a function with is __stdcall calling convention
> When I type:
> (gdb) b Add_S
> Function "Add_S" not defined.
> In fact, the symbol name about "Add_S" function is "Add_S@8", (This can be seen from the disassembler)
> I don't know how to set such breakpoint by function names.

I am not an expert on windows, but it is a bug to me.  People, who know 
more about windows/mingw, can give comments here.

>
> 2, I see there are symbol names for Add_C: one is named "Add_C" and the other is "_imp__Add_C",
> so it has "_imp__" before "Add_C". (One underline prefix and double underlines postfix).

Yes, I can see "_imp__Add_C" too in the output of 'maintenance print 
msymbols'.

-- 
Yao (齐尧)


  reply	other threads:[~2013-07-05 12:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  4:24 Yao Qi
2013-06-27 20:43 ` Tom Tromey
2013-06-28  7:37   ` Yao Qi
2013-06-28 15:58     ` Tom Tromey
2013-07-03  0:26       ` Yao Qi
2013-07-05  8:44         ` asmwarrior
2013-07-05 12:22           ` Yao Qi [this message]
2013-07-05 14:30             ` Eli Zaretskii
2013-07-06  7:21               ` Yao Qi
2013-07-06  7:41                 ` Eli Zaretskii
2013-07-06  8:20                   ` asmwarrior
2013-07-10  6:21         ` Yao Qi
2013-07-10 16:56         ` Tom Tromey
2013-07-18  2:09           ` Yao Qi
2013-07-18  3:26             ` Yao Qi

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=51D6BA7A.7040500@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=asmwarrior@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.com \
    /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