Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jason Molenda <jmolenda@apple.com>
To: Mick Jordan <mick.jordan@oracle.com>
Cc: gdb@sourceware.org
Subject: Re: gdb on Mac OS bpt implementation question
Date: Thu, 10 Nov 2011 22:19:00 -0000	[thread overview]
Message-ID: <02316737-5D19-4720-912A-A8A475940A4D@apple.com> (raw)
In-Reply-To: <4EB9BE43.7050200@oracle.com>


On Nov 8, 2011, at 3:41 PM, 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).


For what it's worth, two other implementations that may be worth consulting on issues like this are the Apple fork of gdb, downloadable here
	http://opensource.apple.com/
although it's based on the gdb sources circa 2006-2007.


lldb, the new debugger that we've been writing recently is licensed under the LLVM copyright (berkeley-style) and has a public svn repository, is also a good reference for how debuggers work on the Mac OS X platform.  v.
	http://lldb.llvm.org/

although note that lldb's primary method of operation on Mac OS X is to debug the inferior via a gdbserver-like program via gdb remote protocol (our implementation is "debugserver" and the sources are in lldb/tools/debugserver in the source checkout).  Originally we had lldb controlling the inferior process directly but on Mac OS X we've moved away from that and have all process done by debugserver - that's where you'd want to look to see how the low level memory reading/writing/etc is done.


Jason


      parent reply	other threads:[~2011-11-10 22:19 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
2011-11-10 22:19 ` Jason Molenda [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=02316737-5D19-4720-912A-A8A475940A4D@apple.com \
    --to=jmolenda@apple.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