From: Petr Sorfa <petrs@caldera.com>
To: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: [RFC] IA64 handling of breakpoints on L in MLX instruction bundles
Date: Wed, 08 May 2002 12:44:00 -0000 [thread overview]
Message-ID: <3CD98303.5B2F08C3@caldera.com> (raw)
Hi,
GDB cannot handle breakpoints on the L instruction type in MLX
instruction bundles.
Current GDB inserts the breakpoint in L (second slot of the bundle). Not
only is this code never executed (it is specifically designed to hold
long integers) it actually changes the value for the associated
instruction (MOVL) in the third slot. So (a) the breakpoint doesn't work
and (b) the actual program has now changed functionally as the
breakpoint will never be hit to revert the instruction bundle to its
correct state.
I have a patch for this. For both the ia64_memory_insert_breakpoint and
ia64_memory_remove_breakpoint routines in ia64-tdep.c a check is made on
the instruction bundle. If it is the second slot and an L type, then the
slot number is bumped up to the 3rd slot. This effectively achieves the
required behaviour.
Is this solution acceptable?
Petr
next reply other threads:[~2002-05-08 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 12:44 Petr Sorfa [this message]
2002-05-08 14:22 ` Kevin Buettner
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=3CD98303.5B2F08C3@caldera.com \
--to=petrs@caldera.com \
--cc=gdb-patches@sources.redhat.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