On Wed, Sep 28, 2005 at 12:06:21PM -0600, Davda, Bhavesh P (Bhavesh) wrote:
> > Yes, I entirely understand what you're saying. I feel like you're not
> > reading my responses. GDB _already has a list of signals it does not
> > care about_. If ptrace permitted, it could tell the kernel not to
> > context switch to deliver those signals. In advance! That's a
> > debugger-driven solution to your problem.
> >
> > I'm not arguing out of theory here. I've implemented this mechanism
> > before in other contexts, for instance to prevent the remote protocol
> > overhead for ignored signals when using gdb with gdbserver.
> >
>
>
> Okay, I'll come up with an alternative patch that enhances the ptrace
> interface so the debugger can guide the kernel to NOT context switch and
> bother it about signal x from task y.
>
> Would you be amenable to such a patch?
Yes, definitely. I just hadn't found a chance to think about what the
interface should look like.
[For the record, I'm pretty sure that the Solaris procfs debug
interface offers a similar feature.]
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|