public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ninive at gmx dot at" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13303] New: strange crash in 64bit vsnprintf()
Date: Sun, 16 Oct 2011 21:27:00 -0000 [thread overview]
Message-ID: <bug-13303-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13303
Bug #: 13303
Summary: strange crash in 64bit vsnprintf()
Product: glibc
Version: 2.11
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper.fsp@gmail.com
ReportedBy: ninive@gmx.at
Classification: Unclassified
Created attachment 5989
--> http://sourceware.org/bugzilla/attachment.cgi?id=5989
Testcase
vsnprintf() crashed on 64bit CentOS, but not on 32bit.
Backtrace (taken from CentOS 5):
#0 0x00000032a7479b60 in strlen () from /lib64/libc.so.6
0000001 0x00000032a7446cb9 in vfprintf () from /lib64/libc.so.6
0000002 0x00000032a74699da in vsnprintf () from /lib64/libc.so.6
#3 0x00000000006023cb in format (this=0x7fff315e9400, params=0xa22238
#4 0x00000000009b3f86 in main (argc=1, argv=0x7fff315e9768)
Tested with
GNU libc: 2.5 (CentOS 5), 2.6.18-274.3.1.el5 x86_64 GNU/Linux
GNU libc: 2.11 (Ubuntu 10.04), 2.6.32-34-server x86_64 GNU/Linux
Steps to reproduce:
wget http://doppelbauer.name/vsnprintf.cpp
g++ -g -o vsnprintf vsnprintf.cpp
./vsnprintf
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-10-16 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 21:27 ninive at gmx dot at [this message]
2011-10-17 7:19 ` [Bug libc/13303] " ninive at gmx dot at
2011-10-17 7:45 ` aj at suse dot de
2011-10-17 8:14 ` ninive at gmx dot at
2014-06-27 11:51 ` fweimer at redhat dot com
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-13303-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).