public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "wuchengping at h3c dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/12958] How to set a breakpoint at the exit of a function?
Date: Wed, 06 Jul 2011 03:45:00 -0000 [thread overview]
Message-ID: <bug-12958-4717-WZzeqD53E4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12958-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12958
--- Comment #3 from 伍成平 <wuchengping at h3c dot com> 2011-07-06 03:44:40 UTC ---
(In reply to comment #1)
> (In reply to comment #0)
> > I know how to set a breakpoint at the begin of a function.it is "break
> > function_name",but how to set a breakpoint at the exit/end of a function?
> you can dissembly the function in gdb, and get the address of exit/end of a
> function, then you can set breakpoint on that address, for example, "b
> *0x123456".
yes,I can set a breakpoint at the exit of a function in this way,but it can
only be used once, because when I modified my code,the exit address of the
function will also change,so I must modify "the gdb command file"
synchronously.I use the gdb command in this way "gdb -p $(pidof vmserver) -x
cmd.txt",and the gdb command lies in the file(cmd.txt).the file content is:
b CDeviceMgr::queryPhyDevsInDomain
command
silent
p pcUserCode
c
end
c
In this way,I can watch the input parameters of the function,but how to watch
the output parameters?
I hope that I can set the exit breakpoint as simple as the entrance
breakpoint.The most important thing is that I hope,when I modified my code,the
gdb command file will be no need to modify synchronously.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-07-06 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 9:21 [Bug breakpoints/12958] New: " wuchengping at h3c dot com
2011-07-06 1:33 ` [Bug breakpoints/12958] " qiyao at gcc dot gnu.org
2011-07-06 3:08 ` wuchengping at h3c dot com
2011-07-06 3:45 ` wuchengping at h3c dot com [this message]
2011-07-07 9:31 ` jan.kratochvil at redhat dot com
2011-07-18 16:26 ` tromey at redhat dot com
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=bug-12958-4717-WZzeqD53E4@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).