public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/14446] New: breakpoints may not work on jitted code
Date: Thu, 09 Aug 2012 19:11:00 -0000 [thread overview]
Message-ID: <bug-14446-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14446
Bug #: 14446
Summary: breakpoints may not work on jitted code
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
AssignedTo: unassigned@sourceware.org
ReportedBy: hjl.tools@gmail.com
Classification: Unclassified
What happens are
1. V8 initializes memory for code with 0xdeadbeef.
2. When you set breakpoint in GDB, gdb saves and replaces one byte,
which happens to be 0xef in 0xdeadbeef, with 0xcc.
3. V8 writes out real instructions in memory.
4. When breakpoint is hit, GDB replaces 0xcc with 0xef.
5. V8 crashes due to 0xef.
--
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 reply other threads:[~2012-08-09 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 19:11 hjl.tools at gmail dot com [this message]
2012-09-17 19:15 ` [Bug breakpoints/14446] " tromey at redhat dot com
2012-09-17 19:40 ` hjl.tools at gmail 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-14446-4717@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).