Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	Hui Zhu <hui_zhu@mentor.com>,
	       gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix interrupt.exp fails with m32 in x86_64
Date: Tue, 29 Apr 2014 17:05:00 -0000	[thread overview]
Message-ID: <535FDBD9.9040803@redhat.com> (raw)
In-Reply-To: <CANFwon2cqqDPTg5hAUzHt0iCEjp8RrJxQf1ETouDU0EKfH+XKQ@mail.gmail.com>

On 04/29/2014 04:56 PM, Hui Zhu wrote:
> I am sorry that the root cause of issue has something wrong.
> The right root cause is:
> When inferior call 32 bits syscall "read", Linux kernel function
> "ia32_cstar_target" will set TS_COMPAT to current_thread_info->status.

Thanks a lot of tracking this stuff down.  I appreciate the effort.

It'd be great if we got an ack on the kernel side on what's
going on before we considered working around it in GDB.

Thanks,
-- 
Pedro Alves


      reply	other threads:[~2014-04-29 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 16:17 Hui Zhu
2014-04-21 18:27 ` Mark Kettenis
2014-04-22 13:09   ` Hui Zhu
2014-04-29 15:57   ` Hui Zhu
2014-04-29 17:05     ` Pedro Alves [this message]

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=535FDBD9.9040803@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=mark.kettenis@xs4all.nl \
    --cc=teawater@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox