From: Andi Kleen <ak@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: akpm@osdl.org, torvalds@osdl.org, mingo@redhat.com,
jparadis@redhat.com, cagney@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-64 support for singlestep into 32-bit system calls
Date: Tue, 13 Jul 2004 09:23:07 +0200 [thread overview]
Message-ID: <20040713092307.4cd6b5aa.ak@suse.de> (raw)
In-Reply-To: <200407122358.i6CNwQ4Q001709@magilla.sf.frob.com>
On Mon, 12 Jul 2004 16:58:26 -0700
Roland McGrath <roland@redhat.com> wrote:
> This patch makes x86-64's 32-bit support behave consistently with the
> native i386 behavior achieved in Davide Libenzi's patch:
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.7/2.6.7-mm7/broken-out/really-ptrace-single-step-2.patch
>
> I hope these both can go into 2.6.8 or 2.6.9, since they make life
> better for gdb.
I would prefer not to merge this. It looks extremly ugly and the current
behaviour is not that unreasonable and gdb has lived with it forever,
so why can't it continue it? It has to keep supporting old versions
anyways and other i386 OS it supports probably do the same.
If i386 merges it I guess it's ok for consistency, but it would be
better to not do it at all.
> +#ifdef CONFIG_IA32_EMULATION
> + clear_tsk_thread_flag(child, TIF_SINGLESTEP);
> +#endif
This looks wrong. Why do you do this unconditionally when 32bit
emulation is compiled in? Either it is correct to do for 64bit
processes, then the ifdef should go, or it is not correct then
it would need a test. For me dropping the flag both for 32bit
and 64bit looks wrong.
Same in other hunks.
-Andi
next prev parent reply other threads:[~2004-07-13 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 23:58 [PATCH] x86-64 support for singlestep into 32-bit system calls Roland McGrath
2004-07-13 7:23 ` Andi Kleen [this message]
2004-07-13 23:48 ` Roland McGrath
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=20040713092307.4cd6b5aa.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=cagney@redhat.com \
--cc=jparadis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=roland@redhat.com \
--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.