From: Sergei Trofimovich <slyfox@gentoo.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
stanton_arch@mail.com
Subject: Re: [PATCH] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb)
Date: Sun, 11 Feb 2018 18:51:34 +0000 [thread overview]
Message-ID: <20180211185134.76ccfd45@sf> (raw)
In-Reply-To: <20180202230220.13b74e8c@sf>
On Fri, 2 Feb 2018 23:02:20 +0000
Sergei Trofimovich <slyfox@gentoo.org> wrote:
> On Fri, 2 Feb 2018 14:22:32 -0800
> "Luck, Tony" <tony.luck@intel.com> wrote:
>
> > On Fri, Feb 02, 2018 at 10:12:24PM +0000, Sergei Trofimovich wrote:
> > > The strace breakage looks like that:
> > > ./strace: get_regs: get_regs_error: Input/output error
> > >
> > > It happens because ia64 needs to load unwind tables
> > > to read certain registers. Unwind tables fail to load
> > > due to GCC quirk on the following code:
> > >
> > > extern char __end_unwind[];
> > > const struct unw_table_entry *end = (struct unw_table_entry *)table_end;
> > > table->end = segment_base + end[-1].end_offset;
> > >
> > > GCC does not generate correct code for this single memory
> > > reference after constant propagation (see https://gcc.gnu.org/PR84184).
> >
> > I'm not seeing this ... probably because I build with
> > a pre-historic 4.3.4 version of gcc.
> >
> > Do you know which version(s) are affected? I'm not looking
> > for an exhaustive list, just the one on which you found this
> > would be good.
> >
> > -Tony
>
> Original bug https://bugs.gentoo.org/518130 claims regression appeared
> around gcc-4.5. Locally am seeing the problem with gcc-6.4.0, gcc-7.2.0 and
> gcc-8 (HEAD).
Another report on the positive patch effect:
rx2600 boots successfully with this patch (did not without, my guess is due to
early access fault at bad address): https://bugs.gentoo.org/579278#c13
Tested-by: stanton_arch@mail.com
--
Sergei
next prev parent reply other threads:[~2018-02-11 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 22:12 [PATCH] ia64: fix ptrace(PTRACE_GETREGS) (unbreaks strace, gdb) Sergei Trofimovich
2018-02-02 22:12 ` Sergei Trofimovich
2018-02-02 22:22 ` Luck, Tony
2018-02-02 22:22 ` Luck, Tony
2018-02-02 23:02 ` Sergei Trofimovich
2018-02-02 23:02 ` Sergei Trofimovich
2018-02-11 18:51 ` Sergei Trofimovich [this message]
2018-03-09 23:15 ` [PATCH v2, simpler] " Sergei Trofimovich
2018-03-09 23:15 ` Sergei Trofimovich
2018-08-04 21:33 ` Sergei Trofimovich
2018-08-04 21:33 ` Sergei Trofimovich
2019-04-29 10:38 ` [PATCH] " John Paul Adrian Glaubitz
2019-04-29 10:38 ` John Paul Adrian Glaubitz
2019-04-29 11:34 ` John Paul Adrian Glaubitz
2019-04-29 11:34 ` John Paul Adrian Glaubitz
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=20180211185134.76ccfd45@sf \
--to=slyfox@gentoo.org \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stanton_arch@mail.com \
--cc=tony.luck@intel.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 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.