From: Adam Jocksch <ajocksch@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: Some trouble writing a testcase
Date: Mon, 14 May 2007 16:47:00 -0000 [thread overview]
Message-ID: <46488CBD.3010508@redhat.com> (raw)
Ok, I'm trying to write a simple testcase for the newly created Display
class and I'm uncovering some of the rust that's built up over that last
few months :P. Essentially the test I want to create consists of having
a program:
int x;
x = 1; *
x = 2; **
Then creating breakpoints at the two lines marked by * and ** and then
printing out the variable values (via Display) at those two points.
Right now I'm using AttachedDaemonProcess to create a proc that's
attached and blocked at the first address of the program. However I'm
having some difficulties find the right sequence of calls to add the
breakpoints. Currently I'm trying LineBreakoint.addLineBreakpoint() and
then adding my own delegate observer to pick up on the calls. Is this
correct, or is there something else I should be doing?
next reply other threads:[~2007-05-14 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 16:47 Adam Jocksch [this message]
2007-05-14 18:04 ` Adam Jocksch
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=46488CBD.3010508@redhat.com \
--to=ajocksch@redhat.com \
--cc=frysk@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).