All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: "strace-devel@lists.strace.io" <strace-devel@lists.strace.io>
Cc: arcml <linux-snps-arc@lists.infradead.org>
Subject: strace breaks with to be released glibc 2.31
Date: Wed, 15 Jan 2020 20:10:38 +0000	[thread overview]
Message-ID: <a3f63e62-e616-5fee-1f31-a09eb25406ef@synopsys.com> (raw)

Hi,

I've been testing an in-works glibc port for ARC and with 2.31 there's a glibc
change which seems to break strace.

Commit d1e411e5c786ce3 "Add PTRACE_GET_SYSCALL_INFO from Linux 5.3 to sys/ptrace.h."

This now defines PTRACE_GET_SYSCALL_INFO but defines struct __ptrace_syscall_info
(not the non underscored ver) causing strace to trip.

I'm not sure how to fix strace: do we need to switch over to glibc provided
__ptrace_syscall_info (with some #ifdef GLIBC and MINOR etc) or is there a better
way to do this ?

Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

             reply	other threads:[~2020-01-15 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 20:10 Vineet Gupta [this message]
2020-01-16 16:52 ` strace breaks with to be released glibc 2.31 Dmitry V. Levin

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=a3f63e62-e616-5fee-1f31-a09eb25406ef@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=strace-devel@lists.strace.io \
    /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.