From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11535 invoked by alias); 27 Oct 2011 19:32:21 -0000 Received: (qmail 11526 invoked by uid 22791); 27 Oct 2011 19:32:21 -0000 X-SWARE-Spam-Status: No, hits=-7.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS,TW_QE X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 27 Oct 2011 19:32:02 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9RJW1YJ025273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Oct 2011 15:32:01 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9RJW0rq004884; Thu, 27 Oct 2011 15:32:01 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9RJVxsZ027792; Thu, 27 Oct 2011 15:31:59 -0400 From: Tom Tromey To: Jan Kiszka Cc: Vimal , gdb@sourceware.org Subject: Re: Multiple breakpoint issue when debugging loadable kernel module References: <4EA89365.2010807@web.de> Date: Thu, 27 Oct 2011 19:38:00 -0000 In-Reply-To: <4EA89365.2010807@web.de> (Jan Kiszka's message of "Thu, 27 Oct 2011 01:10:29 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00205.txt.bz2 >>>>> "Jan" == Jan Kiszka writes: Jan> At least it is a critical one as it makes kernel module debugging nearly Jan> impossible. I'm preparing a LinuxCon talk about how cool kernel Jan> debugging with gdb and qemu can be - looks like I have to skip this Jan> part... ;) Well, we can't let that happen. Jan> If there is anything to be done that could help analyzing the issue, Jan> please let us know. A recipe to reproduce the bug. I know nothing about the kernel, so if it requires extensive setup, precise instructions would be best. We've been poking at it a bit on irc but, aside from a lot of weird and inexplicable gdb behavior, we haven't seen anything too useful. Tom