public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/776] New: Inconsistent struct gconvcache_header Date: Wed, 02 Mar 2005 01:21:00 -0000 [thread overview] Message-ID: <20050302012132.776.hjl@lucon.org> (raw) In iconvconfig.h, there are typedef uint16_t gidx_t; struct gconvcache_header { uint32_t magic; gidx_t string_offset; gidx_t hash_offset; gidx_t hash_size; gidx_t module_offset; gidx_t otherconv_offset; }; But in iconvconfig.c, there are /* Format of the output file. Offset Length Description 0000 4 Magic header bytes 0004 4 Offset of string table (stoff) 0008 4 Offset of name hashing table (hoff) 000C 4 Hashing table size (hsize) 0010 4 Offset of module table (moff) 0014 4 Offset of other conversion module table (ooff) stoff ??? String table The lengths of stoff, hoff, hsize, moff and ooff are 2 not 4. Also compiler may put padding in struct gconvcache_header, which may not be initialized. When write_output does iov[0].iov_base = &header; iov[0].iov_len = sizeof (struct gconvcache_header); total = iov[0].iov_len; we may get different values in padding for different compilers. -- Summary: Inconsistent struct gconvcache_header Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: gotom at debian dot or dot jp ReportedBy: hjl at lucon dot org CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=776 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-03-02 1:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-02 1:21 hjl at lucon dot org [this message] 2005-03-03 8:28 ` [Bug libc/776] " drepper at redhat dot com 2005-03-03 16:28 ` cvs-commit at gcc dot gnu dot org 2005-04-06 0:38 ` roland at gnu dot org 2005-04-06 0:38 ` cvs-commit at gcc dot gnu dot 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=20050302012132.776.hjl@lucon.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.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: 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).