From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <asmwarrior@gmail.com>, <tromey@redhat.com>,
<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix up msymbol type of dll trampoline to mst_solib_trampoline
Date: Sat, 06 Jul 2013 07:21:00 -0000 [thread overview]
Message-ID: <51D7C543.7030905@codesourcery.com> (raw)
In-Reply-To: <8361wpyta1.fsf@gnu.org>
On 07/05/2013 10:29 PM, Eli Zaretskii wrote:
>> Date: Fri, 5 Jul 2013 20:22:18 +0800
>> From: Yao Qi <yao@codesourcery.com>
>> CC: Tom Tromey <tromey@redhat.com>, <gdb-patches@sourceware.org>
>>
>>> 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.
>
> What exactly do you see as a bug here?
>
We can't set breakpoint on 'Add_S' in current GDB,
(gdb) b Add_S
Function "Add_S" not defined.
Make breakpoint pending on future shared library load? (y or [n])
IMO, It is expected that 'b Add_S' can set a breakpoint on Add_S.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-07-06 7:21 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
2013-07-05 14:30 ` Eli Zaretskii
2013-07-06 7:21 ` Yao Qi [this message]
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=51D7C543.7030905@codesourcery.com \
--to=yao@codesourcery.com \
--cc=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--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