RE: symbolic debug of loadable modules with kgdb light

[Caz Yokoyama <cazyokoyama at gmail dot com>]

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