On Thu, Jun 07, 2001 at 09:35:57PM +0200, Maciej W. Rozycki wrote:
> On Thu, 7 Jun 2001, Daniel Jacobowitz wrote:
> > > This happened to me once. Otherwise, it looks like gdb doesn't recognize
> > > a breakpoint for some reason -- possibly it places it at a wrong address.
> > > It shouldn't be difficult to debug -- you get information of the address
> > > the trap happened.
> > Wouldn't you hope? No such luck.
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > [Switching to Thread 1024 (LWP 89)]
> > 0x00000000 in ?? ()
> Then patch your kernel to display the address. It's trivial. See
> do_bp() in arch/mips/kernel/traps.c.
Good idea. Thanks.
> > I blame the threads handling, which I'm only about half through
> > debugging.
> Ah, threads... They might be completely non-fuctional on MIPS/Linux.
> I've never run threaded programs on MIPS/Linux, but such trivial users as
> ls appear to work.
They work, with a couple of kernel patches and a couple of library
patches. I'm sorting through them right now.
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team