This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix addseverity

From: Ulrich Drepper <drepper at redhat dot com>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>
Date: Tue, 25 Jan 2005 14:15:01 -0800
Subject: Re: [PATCH] Fix addseverity
Organization: Red Hat, Inc.
References: <20050125221300.GM4777@sunsite.mff.cuni.cz>

Jakub Jelinek wrote:

if the string passed to addseverity is freed by the caller,
we still reference freed up memory, or if the string passed to addseverity
is overwritten, we use whatever it was overwritten to.

I've never seen anything to the contrary that this is acceptable. The function is not part of any spec and when I wrote this code this seemed to be what other implementations did. What program has problems with the current code?

--
â Ulrich Drepper â Red Hat, Inc. â 444 Castro St â Mountain View, CA â

Attachment: signature.asc
Description: OpenPGP digital signature

Follow-Ups:
- [PATCH] Fix addseverity (take 2)
  - From: Jakub Jelinek

References:
- [PATCH] Fix addseverity
  - From: Jakub Jelinek

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]