public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [Bug breakpoints/14446] New: breakpoints may not work on jitted code
@ 2012-08-09 19:11 hjl.tools at gmail dot com
2012-09-17 19:15 ` [Bug breakpoints/14446] " tromey at redhat dot com
2012-09-17 19:40 ` hjl.tools at gmail dot com
0 siblings, 2 replies; 3+ messages in thread
From: hjl.tools at gmail dot com @ 2012-08-09 19:11 UTC (permalink / raw)
To: gdb-prs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug breakpoints/14446] breakpoints may not work on jitted code 2012-08-09 19:11 [Bug breakpoints/14446] New: breakpoints may not work on jitted code hjl.tools at gmail dot com @ 2012-09-17 19:15 ` tromey at redhat dot com 2012-09-17 19:40 ` hjl.tools at gmail dot com 1 sibling, 0 replies; 3+ messages in thread From: tromey at redhat dot com @ 2012-09-17 19:15 UTC (permalink / raw) To: gdb-prs http://sourceware.org/bugzilla/show_bug.cgi?id=14446 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at redhat dot com --- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-09-17 19:14:46 UTC --- Could you elaborate on when gdb can put a breakpoint into uninitialized memory? -- 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug breakpoints/14446] breakpoints may not work on jitted code 2012-08-09 19:11 [Bug breakpoints/14446] New: breakpoints may not work on jitted code hjl.tools at gmail dot com 2012-09-17 19:15 ` [Bug breakpoints/14446] " tromey at redhat dot com @ 2012-09-17 19:40 ` hjl.tools at gmail dot com 1 sibling, 0 replies; 3+ messages in thread From: hjl.tools at gmail dot com @ 2012-09-17 19:40 UTC (permalink / raw) To: gdb-prs http://sourceware.org/bugzilla/show_bug.cgi?id=14446 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2012-09-17 19:40:01 UTC --- (In reply to comment #1) > Could you elaborate on when gdb can put a breakpoint into > uninitialized memory? We can set a watchpoint on the breakpoint and catch the new value. GDB restores the new value instead of the old saved value. -- 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-09-17 19:40 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2012-08-09 19:11 [Bug breakpoints/14446] New: breakpoints may not work on jitted code hjl.tools at gmail dot com 2012-09-17 19:15 ` [Bug breakpoints/14446] " tromey at redhat dot com 2012-09-17 19:40 ` hjl.tools at gmail dot com
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).