Re: KDB support for x86_64?

Nigel Cunningham <[email protected]>
Newsgroups gmane.linux.kernel.debugging
Organization Cyclades Corporation
Message-ID <[email protected]>
Hi.
On Saturday 01 April 2006 19:36, Peter Wainwright wrote:
> On Sun, 2006-03-26 at 17:32 -0800, Jack Vogel wrote:
> > On Mon, Mar 27, 2006 at 08:00:46AM +1000, Nigel Cunningham wrote:
> > > Hi.
> > >
> > > On Sunday 26 March 2006 21:58, Peter Wainwright wrote:
> > > > Is KDB still maintained for the x86_64 architecture? oss.sgi.com has
> > > > x86_64 patches for kernel 2.6.14 but not for more recent
> > > > kernels. I tried to forward-port it to 2.6.16 myself but it is
> > > > not giving a proper backtrace (%rsp seems to be wrong at
> > > > breakpoints).
> > > >
> > > > Peter Wainwright
> > >
> > > I would find it useful too. I've forward ported it as well, and also
> > > have the same backtrace problem. I guess it's probably simple to fix,
> > > but it doesn't irk me enough that I've bothered to try to fix it.
> > >
> > > Regards,
> > >
> > > Nigel
> >
> > Did you have the problem with the last patch, there was
> > some backtrace changes that I accepted that I did not have
> > time to test. It would be useful if you could check a before
> > and after of that code.
> >
> > Regards,
> >
> > Jack
>
> The change I mentioned in the previous mail actually seems to
> simplify things for the debugger, since SS/SP is now saved on
> the interrupt stack at breakpoints.
> This patch seems to work for me. Unless you can find some path
> into kdba_getregcontents where SS/SP is NOT saved in regs?

I'll give it a go.

Regards,

Nigel


-- Attached file included as plaintext by Ecartis --

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBELkoDN0y+n1M3mo0RApAxAKDCgh8kLSZ+eLLogV961HVlzu91igCg6pDr
vNQZpxqVTCEUs2RKQSZuhBI=
=274P
-----END PGP SIGNATURE-----


---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.