Re: ptrace single-stepping change breaks Wine
From: Linus Torvalds (torvalds_at_osdl.org)
Date: 12/31/04
- Previous message: Linus Torvalds: "Re: ptrace single-stepping change breaks Wine"
- In reply to: Daniel Jacobowitz: "Re: ptrace single-stepping change breaks Wine"
- Next in thread: Andi Kleen: "Re: ptrace single-stepping change breaks Wine"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 31 Dec 2004 09:19:48 -0800 (PST) To: Daniel Jacobowitz <dan@debian.org>
On Fri, 31 Dec 2004, Daniel Jacobowitz wrote:
>
> Lots, I like it. The syscall trap will always be delivered before the
> single-step trap, right, because signal delivery won't run until we
> return to userspace?
Yes. Although I've not actually tested it.
Before, it used to show up as one event, and basically the "0x80" marker
got lost, so effectively the "system call exit" part would have got lost.
Now, it _may_ DTRT, with the caveat that the system call ptrace_notify()
thing still has the same problem with restarting-with-a-signal.
That's basically a "don't do that then", and is the status quo, of course,
so this is at least not a regression. It's still pretty ugly, but
apparently nobody really cares ;)
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Linus Torvalds: "Re: ptrace single-stepping change breaks Wine"
- In reply to: Daniel Jacobowitz: "Re: ptrace single-stepping change breaks Wine"
- Next in thread: Andi Kleen: "Re: ptrace single-stepping change breaks Wine"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
