From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Frederic Weisbecker <fweisbec@gmail.com>, Ingo Molnar <mingo@elte.hu>
Subject: [2.6.32.git] commit 1cedae7 breaks gdb
Date: Sun, 06 Dec 2009 17:03:20 -0800 [thread overview]
Message-ID: <4B1C5458.1030707@gmail.com> (raw)
Hi guys. This commit:
commit 1cedae72904b85462082dbcfd5190309ba37f8bd
Author: Frederic Weisbecker <fweisbec@gmail.com>
Date: Wed Dec 2 07:32:16 2009 +0100
hw-breakpoints: Keep track of user disabled breakpoints
breaks debugging with gdb (at least gdb-7.0, anyway).
For example, if you start firefox with the -g flag, it will run
in gdb. When running a kernel with this commit, gdb will stop
with the message: "Couldn't write debug register: No space left
on device". When trying to quit gdb by typing 'q', the process
hangs forever.
This seems to be related to the size of the program being debugged.
Running /bin/ls with gdb, for example, works normally. But large
programs like firefox, thunderbird, or evolution (from gnome) all
trigger the same error message.
Can anyone reproduce this?
Thanks.
next reply other threads:[~2009-12-07 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 1:03 walt [this message]
2009-12-07 15:54 ` [2.6.32.git] commit 1cedae7 breaks gdb walt
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=4B1C5458.1030707@gmail.com \
--to=w41ter@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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