public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vda dot linux at googlemail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/364] strerror_r does not copy error string to user supplied buffer
Date: Tue, 04 Jul 2006 11:57:00 -0000	[thread overview]
Message-ID: <20060704115704.15220.qmail@sourceware.org> (raw)
In-Reply-To: <20040902190535.364.dancasimiro@alum.rpi.edu>


------- Additional Comments From vda dot linux at googlemail dot com  2006-07-04 11:57 -------
Because I'm tracking down obscure bug in svn (seemingly),
and tracked it down to strerror_r not updating buffer 
and _not_ returning -1.

From: Denis Vlasenko <vda.linux@googlemail.com>
To: Malcolm Rowe <malcolm-svn-dev@farside.org.uk>
Subject: Re: BUG: svn enters unkillable state, tracked down to UTF conv in locale!=C
Date: Tue, 4 Jul 2006 13:53:59 +0200

> If your native_strerror() looks like that, you must have STRERROR_R_RC_INT
> defined (in APR's include/arch/unix/apr_private.h), which implies you're
> using the platform-native C library for either AIX or Tru64 (from the
> comments in the above file).
>
> I thought you were using glibc?  What OS are you using?

It _is_ glibc 2.4. Looks like glibc people switched to POSIX version
of strerror_r. See here:

http://sources.redhat.com/bugzilla/show_bug.cgi?id=364

But sometimes it returns >=0, yet buffer is not modified.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=364

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-07-04 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 19:05 [Bug libc/364] New: " dancasimiro at alum dot rpi dot edu
2004-09-02 19:07 ` [Bug libc/364] " dancasimiro at alum dot rpi dot edu
2004-09-02 21:07 ` schwab at suse dot de
2006-07-04 11:22 ` vda dot linux at googlemail dot com
2006-07-04 11:40 ` jakub at redhat dot com
2006-07-04 11:57 ` vda dot linux at googlemail dot com [this message]
2006-07-04 13:32 ` vda dot linux at googlemail 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=20060704115704.15220.qmail@sourceware.org \
    --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).