All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Marques <pmarques@grupopie.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: Trap flag handling change in 2.6.10-bk5 broke Kylix  debugger
Date: Wed, 15 Feb 2006 17:46:34 +0000	[thread overview]
Message-ID: <43F368FA.7000000@grupopie.com> (raw)
In-Reply-To: <200602142220_MC3-1-B866-DF84@compuserve.com>

Chuck Ebbert wrote:
> On Tue, 14 Feb 2006 at 20:21:08 +0000, Paulo Marques wrote:
> 
>>>+                   regs->eflags &= ~TF_MASK;
>>>+                   tsk->ptrace &= ~PT_DTRACE;
>>>+                   if (!tsk->ptrace & PT_DTRACE)
> 
>                             ^^^^^^^^^^^^^^^^^^^^^^^^
>   Looks like this is always true because that bit was cleared one line above.
> Maybe it should be testing PT_DTRACED instead?  And it's missing parens too,
> so try:
>                         if (!(tsk->ptrace & PT_DTRACED))

Yes, this does look funny :P

However, this is the piece of code that I don't put in in order to make 
the debugger work, and it doesn't exist on the vanilla 2.6.16-rc kernel 
anymore.

What I did try to do was to add the:

-           if ((tsk->ptrace & (PT_DTRACE|PT_PTRACED)) == PT_DTRACE)
-                   goto clear_TF;

condition to the 2.6.16-rc kernel, but that didn't work anyway :(

-- 
Paulo Marques - www.grupopie.com

Pointy-Haired Boss: I don't see anything that could stand in our way.
            Dilbert: Sanity? Reality? The laws of physics?

  reply	other threads:[~2006-02-15 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15  3:17 Trap flag handling change in 2.6.10-bk5 broke Kylix debugger Chuck Ebbert
2006-02-15 17:46 ` Paulo Marques [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-14 20:21 Paulo Marques
2006-02-14 20:52 ` Linus Torvalds
2006-02-15 17:43   ` Paulo Marques

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43F368FA.7000000@grupopie.com \
    --to=pmarques@grupopie.com \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.