From: Tristan Gingold <gingold@adacore.com>
To: Mick Jordan <mick.jordan@oracle.com>
Cc: gdb@sourceware.org
Subject: Re: gdb on Mac OS bpt implementation question
Date: Wed, 09 Nov 2011 07:48:00 -0000 [thread overview]
Message-ID: <FB514BC0-FF29-46CC-AFFD-E2F9A91FF663@adacore.com> (raw)
In-Reply-To: <4EB9BE43.7050200@oracle.com>
On Nov 9, 2011, at 12:41 AM, Mick Jordan wrote:
> I'd be grateful if someone could point me to where in the gdb source code that Mac OS specific breakpoint setting is done. The problem I am trying to resolve is how breakpoints are set in shared libraries, given that they are loaded read-only on Mac OS X (assuming the "write a bpt instruction" approach). The context for this is a custom debugger we have for a Java VM (Maxine) which uses "write a bpt instruction" and works fine setting breakpoints in shared library code on Linux and Solaris, but not on MacOS (we get access faults trying to write the BPT instruction).
>
See darwin-nat.c:darwin_read_write_inferior.
If you want to write to a page, you have to make it writable.
Tristan.
next prev parent reply other threads:[~2011-11-09 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 23:42 Mick Jordan
2011-11-09 7:48 ` Tristan Gingold [this message]
2011-11-10 22:19 ` Jason Molenda
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=FB514BC0-FF29-46CC-AFFD-E2F9A91FF663@adacore.com \
--to=gingold@adacore.com \
--cc=gdb@sourceware.org \
--cc=mick.jordan@oracle.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