public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kiszka at siemens dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/17837] python-injected silent breakpoints broken since 1a853c52
Date: Wed, 04 Feb 2015 18:17:00 -0000	[thread overview]
Message-ID: <bug-17837-4717-lYybUNHGAy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17837-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17837

--- Comment #10 from Jan Kiszka <jan.kiszka at siemens dot com> ---
Tried this path but didn't succeed so far. While I was able to shrink down the
kernel-based reproduction case on basically

    class LoadModuleBreakpoint(gdb.Breakpoint):
        ....
        def stop(self):
            cmdline = "add-symbol-file /path/module.ko 0xffffffffa05f0000"
            gdb.execute(cmdline, to_string=True)
            return False

and still get the bug, using a normal userspace application with the same
binary added on breakpoint hit does not trigger it.

Could it be that the vmlinux layout makes the difference here?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


      parent reply	other threads:[~2015-02-04 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 14:43 [Bug python/17837] New: " jan.kiszka at siemens dot com
2015-01-13 15:22 ` [Bug python/17837] " palves at redhat dot com
2015-01-13 15:41 ` jan.kiszka at siemens dot com
2015-01-13 16:07 ` palves at redhat dot com
2015-01-13 16:13 ` jan.kiszka at siemens dot com
2015-01-13 16:21 ` palves at redhat dot com
2015-01-14  7:19 ` jan.kiszka at siemens dot com
2015-01-27 22:36 ` jan.kiszka at siemens dot com
2015-01-31 14:38 ` palves at redhat dot com
2015-02-03 20:32 ` palves at redhat dot com
2015-02-04 18:17 ` jan.kiszka at siemens dot com [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=bug-17837-4717-lYybUNHGAy@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).