Re: setjmp/longjmp hooks for kgdb 2.0.2

[Amit S. Kale]

On Friday 16 Jan 2004 9:27 pm, Tom Rini wrote:
> On Thu, Jan 15, 2004 at 10:52:30AM +0530, Amit S. Kale wrote:
> > Hi Tom,
> >
> > It's nice to see someone working on integrating powerpc kgdb with
> > mainline kgdb. There are a lot of features (like thread lists, gdb
> > deatch-reattach, automodule loading) powerpc kgdb will inherit
> > automatically from common core.
> >
> > setjmp, longjmp isn't required. search_exception_tables take care of
> > invalid memory accesses by kgdb.
> >
> > In arch/ppc/mm/fault.c:do_page_fault, call bad_page_fault if
> > debugger_memerr_expected is non-zero instead of holding mmap_sem.
> >
> > bad_page_fault calls search_exception_tables at the begining. It takes
> > care of invalid memory addresses by kgdb as kgdb uses get_user, put_user
> > to access memory when the access can fail.
>
> OK, thanks.
>
> > For powerpc arch specific code (like entry.S) look at
> > http://kgdb.sourceforge.net/linux-2.4.23-kgdb-1.9.patch
> > It contains powerpc arch specific code for kgdb. I was never able to test
> > this code, so I don't know whether it works.
>
> It might work on some subset of machines, but the serial driver is still
> broken for SERIAL_IO_MEM machines (which there are a lot of) nor is the
> ppc 8xx (which is what I would assume TimeSys used) serial driver
> patched up.

Yes. There is a lot of #ifdef CONFIG_KGDB code in their 
arch/ppc/8260_io/uart.c If your ppc machine uses the same uart, please let me 
know and I'll send you this file.

Which test machine do you have?

> > If you modify kgdb core as well as arch specific files, please try to
> > send separate patches. Single patch will require me to do more work when
> > I merge it against separate patches.
>
> OK.  I _hope_ to get you a patch for the serial stuff shortly.

-- 
Amit Kale
EmSysSoft (http://www.emsyssoft.com)
KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/