public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/14989] dlerror() returns garbage
Date: Mon, 31 Dec 2012 15:10:00 -0000 [thread overview]
Message-ID: <bug-14989-131-C6qcdEvE9d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14989-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14989
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #3 from Rich Felker <bugdal at aerifal dot cx> 2012-12-31 15:10:36 UTC ---
No, failure is not expected. Undefined behavior is expected. Undefined behavior
is completely different from failure. If your program causes undefined
behavior, all bets are off. There is absolutely no requirement on any output of
the program, not even output that was logically generated before the undefined
behavior was invoked. Programs which invoke undefined behavior are completely
invalid and any bug report referring to the behavior of a program that has
invoked undefined behavior is invalid.
--
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 prev parent reply other threads:[~2012-12-31 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 8:23 [Bug dynamic-link/14989] New: " Arfrever.FTA at GMail dot Com
2012-12-31 0:20 ` [Bug dynamic-link/14989] " bugdal at aerifal dot cx
2012-12-31 9:18 ` Arfrever.FTA at GMail dot Com
2012-12-31 15:10 ` bugdal at aerifal dot cx [this message]
2013-01-01 10:12 ` Arfrever.FTA at GMail dot Com
2013-01-01 21:27 ` bugdal at aerifal dot cx
2013-01-10 18:56 ` bugdal at aerifal dot cx
2013-10-11 19:42 ` neleai at seznam dot cz
2013-10-11 21:31 ` bugdal at aerifal dot cx
2014-06-14 5:28 ` fweimer at redhat dot com
2014-06-26 13:38 ` 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-14989-131-C6qcdEvE9d@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: 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).