public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bart.vanassche at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29578] New: Definition of SUN_LEN() is wrong Date: Fri, 16 Sep 2022 23:30:38 +0000 [thread overview] Message-ID: <bug-29578-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29578 Bug ID: 29578 Summary: Definition of SUN_LEN() is wrong Product: glibc Version: 2.38 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: bart.vanassche at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- $ PAGER= git grep -A1 'define SUN_LEN' socket/sys/un.h:# define SUN_LEN(ptr) ((size_t) (((struct sockaddr_un *) 0)->sun_path) \ socket/sys/un.h- + strlen ((ptr)->sun_path)) An ampersand (&) is missing after (size_t). The commit that introduced this incorrect definition is d38cd08ca397 ("update from main archive 961229"). -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-16 23:30 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-16 23:30 bart.vanassche at gmail dot com [this message] 2022-09-17 6:47 ` [Bug libc/29578] " schwab@linux-m68k.org 2022-09-17 23:48 ` bart.vanassche at gmail dot com 2022-09-18 11:27 ` schwab@linux-m68k.org 2022-10-10 7:35 ` schwab@linux-m68k.org
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=bug-29578-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).