linux-mips
[Top] [All Lists]

Re: Debugging using GDB and gdbserver

To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Subject: Re: Debugging using GDB and gdbserver
From: Justin Wojdacki <justin.wojdacki@analog.com>
Date: Sat, 15 Jun 2002 16:05:36 -0700
Cc: linux-mips@oss.sgi.com
Organization: Analog Devices, Communications Processors Group
References: <3D0B9D14.BFE27F7E@analog.com> <20020615151413.A19123@crack.them.org> <3D0BA3C4.79ED2B5D@analog.com> <20020615153831.B19123@crack.them.org> <3D0BBCA5.5A0D722A@analog.com> <20020615172645.A19472@crack.them.org> <3D0BC248.16CB7EC2@analog.com> <20020615180325.B19472@crack.them.org>
Reply-to: justin.wojdacki@analog.com
Sender: owner-linux-mips@oss.sgi.com
Daniel Jacobowitz wrote:
> 
> What should happen is that the child receives a signal (SIGTRAP) after
> the exception.  Then it is scheduled again, drops into do_signal, and
> the kernel notices that the traced bit is set and wakes the tracer.  I'd
> guess your board needs to do something different to deliver the SIGTRAP
> properly, if that isn't happening.
> 
> --
> Daniel Jacobowitz                           Debian GNU/Linux Developer
> MontaVista Software                         Carnegie Mellon University

Okay, thanks for the clarification. :)

-- 
-------------------------------------------------
Justin Wojdacki        
justin.wojdacki@analog.com         (408) 350-5032
Communications Processors Group -- Analog Devices

<Prev in Thread] Current Thread [Next in Thread>