From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4136 invoked by alias); 29 Sep 2009 04:58:56 -0000 Received: (qmail 4125 invoked by uid 22791); 29 Sep 2009 04:58:55 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-yw0-f171.google.com (HELO mail-yw0-f171.google.com) (209.85.211.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 29 Sep 2009 04:58:48 +0000 Received: by ywh1 with SMTP id 1so5560290ywh.25 for ; Mon, 28 Sep 2009 21:58:46 -0700 (PDT) Received: by 10.150.1.12 with SMTP id 12mr9303415yba.210.1254200326230; Mon, 28 Sep 2009 21:58:46 -0700 (PDT) Received: from xpjpn (pool-71-111-147-240.ptldor.dsl-w.verizon.net [71.111.147.240]) by mx.google.com with ESMTPS id 16sm268262gxk.11.2009.09.28.21.58.36 (version=SSLv3 cipher=RC4-MD5); Mon, 28 Sep 2009 21:58:45 -0700 (PDT) From: Caz Yokoyama To: "'Joel Brobecker'" Cc: "'Pedro Alves'" , References: <8AA4B846934A4A9081F778449B96F416@xpjpn> <4A0DE914.1050800@vmware.com> <20090923004802.GA20859@adacore.com> <9ECED0F0DCF04CC185B027503876430D@xpjpn> <20090925160627.GB5077@adacore.com> <66E35EA6599040F894D040E4F50389D0@xpjpn> <535d47e30909260627n662135a1hf6d1a0bb33368b3a@mail.gmail.com> <20090929015830.GJ9003@adacore.com> <1724490614004CEB9EE1A091A151E05B@xpjpn> <20090929042226.GK9003@adacore.com> Subject: RE: symbolic debug of loadable modules with kgdb light Date: Tue, 29 Sep 2009 04:58:00 -0000 Message-ID: <2C14068798BA41219F3603CDD24C8BC0@xpjpn> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20090929042226.GK9003@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00906.txt.bz2 Hello Joel, >We can discuss a solution to that issue if you tell us what the possible >variations are. I know Magic SysRq is the one for Linux kernel. I planned to propose BREAK for Xen hypervisor if my patch were approved. I don't know what interrupt_sequence is on other OSes. However, I believe that introducing the possible variations into gdb is not your intention. You don't want to change the code when OS changes its interrupt_sequence or supporting new OS. >Please let us also know if you'd prefer someone else to review your patches. I am new to gdb mailing list. I know nobody who is a maintainer of gdb. -caz -----Original Message----- From: Joel Brobecker [mailto:brobecker@adacore.com] Sent: Monday, September 28, 2009 9:22 PM To: Caz Yokoyama Cc: 'Pedro Alves'; gdb-patches@sourceware.org Subject: Re: symbolic debug of loadable modules with kgdb light > However, when we debug kernel, interrupt_sequence is varied from kernel to > kernel. It means interrupt_sequence depends on each kernel. To check > correctness of interrupt_sequence, we have to know which kernel we are > debugging. It introduces dependency of kernel. As the result, it is > impossible to satisfy both 1) and 2). I give up. Thank you for reviewing my > patches. You have to believe me when I say that I'm very sorry to hear that. We've both invested a lot of time on these patches, it's a shame to give up when we're so close to a solution. There was one part that I wasn't aware of until you mentioned it, which is the fact that the interrupt sequence varies from kernel to kernel. We can discuss a solution to that issue if you tell us what the possible variations are. Please let us also know if you'd prefer someone else to review your patches. -- Joel