From: Michal Lesniewski <m.lesniewski@samsung.com>
To: 'John Gilmore' <gnu@toad.com>, 'Pedro Alves' <palves@redhat.com>
Cc: gdb@sourceware.org, 'Yao Qi' <yao@codesourcery.com>
Subject: RE: Implementation of different software breakpoint kinds in gdb server
Date: Fri, 19 Oct 2012 08:51:00 -0000 [thread overview]
Message-ID: <000801cdadd6$da8a3670$8f9ea350$%lesniewski@samsung.com> (raw)
In-Reply-To: <201210190028.q9J0Sd2N005583@new.toad.com>
Ok, so all this really looks like a lot of work. I think first I'll have a
look at the code in mem-break.c and try to add support for different kinds
of breakpoints. This must be done first anyway, I guess. I'll let you know
about my results, observations and further ideas.
Thank you for your time and comments :-)
Michal Lesniewski
prev parent reply other threads:[~2012-10-19 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 9:23 Michal Lesniewski
2012-10-18 10:08 ` Pedro Alves
2012-10-18 10:28 ` Yao Qi
2012-10-18 10:42 ` Pedro Alves
2012-10-18 11:44 ` Michal Lesniewski
2012-10-18 12:01 ` Pedro Alves
2012-10-19 0:31 ` John Gilmore
2012-10-19 8:51 ` Michal Lesniewski [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='000801cdadd6$da8a3670$8f9ea350$%lesniewski@samsung.com' \
--to=m.lesniewski@samsung.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=palves@redhat.com \
--cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).