public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/15299] Verify breakpoint bytes when removing the breakpoint
Date: Sun, 24 Mar 2013 11:13:00 -0000	[thread overview]
Message-ID: <bug-15299-4717-uFSl3QdAqX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15299-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15299

--- Comment #5 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2013-03-24 11:13:11 UTC ---
hbreak is dependent on target arch.  And target arch is known only after the
target is running.  If you do "start" then "hbreak" works in FSF GDB.

Yes, sometimes it should be fixed in FSF GDB, you can submit an appropriate
patch to gdb-patches, the Fedora one is:
http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-bz541866-rwatch-before-run.patch

-- 
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.


  parent reply	other threads:[~2013-03-24 11:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24  8:15 [Bug gdb/15299] New: Error memory write when debugging self-modifying code SztfG at yandex dot ru
2013-03-24  8:51 ` [Bug gdb/15299] Verify breakpoint bytes when removing the breakpoint jan.kratochvil at redhat dot com
2013-03-24  9:15 ` SztfG at yandex dot ru
2013-03-24  9:25 ` jan.kratochvil at redhat dot com
2013-03-24  9:56 ` SztfG at yandex dot ru
2013-03-24 11:13 ` jan.kratochvil at redhat dot com [this message]
2013-03-24 13:45 ` SztfG at yandex dot ru
2013-03-24 17:07 ` SztfG at yandex dot ru
2013-03-25 12:12 ` SztfG at yandex dot ru
2013-03-25 12:22 ` jan.kratochvil at redhat dot com
2013-03-25 21:46 ` SztfG at yandex dot ru
2013-03-27 18:28 ` jan.kratochvil at redhat 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-15299-4717-uFSl3QdAqX@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).