[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [CPROG] memory mangement - leak forbyggelse.





Christian Hemmingsen wrote:

"Klaus S. Madsen" <sslug@sslug> writes:

Der er som udgangspunkt ikke et problem med strerror og tråede
programmer, da den returnerer en pointer til et statisk array af
strenge i næsten alle tilfælde. Kun hvis errnum ikke er en gyldig
fejlbesked, overskriver den informationerne i en streng.


Forkert. For som der står om strerror_r i (g)libc info siderne: " This function (strerror_r) should always be used in multi-threaded programs since there is no way to guarantee the string returned by `strerror' really belongs to the last call of the current thread.


Hvorledes skal man finde saadanne informationer.


Jeg har provet

man -k strerror

Resultat

hstrerror
pam_strerror
strerror

info strerror_r giver ikke noget
info strerror giver samme som man strerror
Saa paa mit linux (RedHat 7.1) system kan jeg ikke finde noget om strerror_r, eller
lign. Hvor har du fundet dette information ??


mvh
   mike




 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 20:09 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *