|
From: <sv...@va...> - 2009-08-19 22:01:59
|
Author: sewardj Date: 2009-08-19 23:01:48 +0100 (Wed, 19 Aug 2009) New Revision: 408 Log: Update release notes for 3.5.0. Modified: trunk/docs/manual/dist.news.html Modified: trunk/docs/manual/dist.news.html =================================================================== --- trunk/docs/manual/dist.news.html 2009-08-19 21:57:34 UTC (rev 407) +++ trunk/docs/manual/dist.news.html 2009-08-19 22:01:48 UTC (rev 408) @@ -1,17 +1,17 @@ <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> -<title>4.NEWS</title> +<title>2.NEWS</title> <link rel="stylesheet" href="vg_basic.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.69.1"> <link rel="start" href="index.html" title="Valgrind Documentation"> <link rel="up" href="dist.html" title="Valgrind Distribution Documents"> -<link rel="prev" href="dist.install.html" title="3.INSTALL"> -<link rel="next" href="dist.readme.html" title="5.README"> +<link rel="prev" href="dist.authors.html" title="1.AUTHORS"> +<link rel="next" href="dist.readme.html" title="3.README"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <div><table class="nav" width="100%" cellspacing="3" cellpadding="3" border="0" summary="Navigation header"><tr> -<td width="22px" align="center" valign="middle"><a accesskey="p" href="dist.install.html"><img src="images/prev.png" width="18" height="21" border="0" alt="Prev"></a></td> +<td width="22px" align="center" valign="middle"><a accesskey="p" href="dist.authors.html"><img src="images/prev.png" width="18" height="21" border="0" alt="Prev"></a></td> <td width="25px" align="center" valign="middle"><a accesskey="u" href="dist.html"><img src="images/up.png" width="21" height="18" border="0" alt="Up"></a></td> <td width="31px" align="center" valign="middle"><a accesskey="h" href="index.html"><img src="images/home.png" width="27" height="20" border="0" alt="Up"></a></td> <th align="center" valign="middle">Valgrind Distribution Documents</th> @@ -19,9 +19,575 @@ </tr></table></div> <div class="chapter" lang="en"> <div class="titlepage"><div><div><h2 class="title"> -<a name="dist.news"></a>4.NEWS</h2></div></div></div> +<a name="dist.news"></a>2.NEWS</h2></div></div></div> <div class="literallayout"><p><br> <br> +Release3.5.0(19August2009)<br> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br> +3.5.0isafeaturereleasewithmanysignificantimprovementsandthe<br> +usualcollectionofbugfixes.ThemainimprovementisthatValgrind<br> +nowworksonMacOSX.<br> +<br> +ThisreleasesupportsX86/Linux,AMD64/Linux,PPC32/Linux,PPC64/Linux<br> +andX86/Darwin.Supportforrecentdistrosandtoolchaincomponents<br> +(glibc2.10,gcc4.5)hasbeenadded.<br> +<br> +-------------------------<br> +<br> +Hereisashortsummaryofthechanges.Detailsareshownfurther<br> +down:<br> +<br> +*SupportforMacOSX(10.5.x).<br> +<br> +*ImprovementsandsimplificationstoMemcheck'sleakchecker.<br> +<br> +*ClarificationandsimplificationsinvariousaspectsofValgrind's<br> +textoutput.<br> +<br> +*XMLoutputforHelgrindandPtrcheck.<br> +<br> +*PerformanceandstabilityimprovementsforHelgrindandDRD.<br> +<br> +*Genuinelyatomicsupportforx86/amd64/ppcatomicinstructions.<br> +<br> +*Anewexperimentaltool,BBV,usefulforcomputerarchitecture<br> +research.<br> +<br> +*ImprovedWinesupport,includingabilitytoreadWindowsPDB<br> +debuginfo.<br> +<br> +-------------------------<br> +<br> +Herearedetailsoftheabovechanges,followedbydescriptionsof<br> +manyotherminorchanges,andalistoffixedbugs.<br> +<br> +<br> +*ValgrindnowrunsonMacOSX.(NotethatMacOSXissometimes<br> +called"Darwin"becausethatisthenameoftheOScore,whichisthe<br> +levelthatValgrindworksat.)<br> +<br> +Supportedsystems:<br> +<br> +-ItrequiresOS10.5.x(Leopard).Portingto10.4.xisnotplanned<br> +becauseitwouldrequireworkand10.4isonlybecominglesscommon.<br> +<br> +-32-bitprogramsonx86andAMD64(a.k.ax86-64)machinesaresupported<br> +fairlywell.For10.5.x,32-bitprogramsarethedefaultevenon<br> +64-bitmachines,soithandlesmostcurrentprograms.<br> +<br> +-64-bitprogramsonx86andAMD64(a.k.ax86-64)machinesarenot<br> +officiallysupported,butsimpleprogramsatleastwillprobablywork.<br> +However,start-upisslow.<br> +<br> +-PowerPCmachinesarenotsupported.<br> +<br> +Thingsthatdon'twork:<br> +<br> +-ThePtrchecktool.<br> +<br> +-Objective-Cgarbagecollection.<br> +<br> +---db-attach=yes.<br> +<br> +-IfyouhaveRogueAmoeba's"InstantHijack"programinstalled,<br> +ValgrindwillfailwithaSIGTRAPatstart-up.See<br> +https://bugs.kde.org/show_bug.cgi?id=193917fordetailsanda<br> +simplework-around.<br> +<br> +Usagenotes:<br> +<br> +-Youwilllikelyfind--dsymutil=yesausefuloption,aserror<br> +messagesmaybeimprecisewithoutit.<br> +<br> +-MacOSXsupportisnewandthereforewillbelessrobustthanthe<br> +Linuxsupport.Pleasereportanybugsyoufind.<br> +<br> +-ThreadedprogramsmayrunmoreslowlythanonLinux.<br> +<br> +ManythankstoGregParkerfordevelopingthisportoverseveralyears.<br> +<br> +<br> +*Memcheck'sleakcheckerhasbeenimproved.<br> +<br> +-Theresultsfor--leak-check=summarynowmatchthesummaryresults<br> +for--leak-check=full.Previouslytheycoulddifferbecause<br> +--leak-check=summarycounted"indirectlylost"blocksand<br> +"suppressed"blocksas"definitelylost".<br> +<br> +-Blocksthatareonlyreachableviaatleastoneinterior-pointer,<br> +butaredirectlypointedtobyastart-pointer,werepreviously<br> +markedas"stillreachable".Theyarenowcorrectlymarkedas<br> +"possiblylost".<br> +<br> +-Thedefaultvalueforthe--leak-resolutionoptionhasbeen<br> +changedfrom"low"to"high".Ingeneral,thismeansthatmore<br> +leakreportswillbeproduced,buteachleakreportwilldescribe<br> +fewerleakedblocks.<br> +<br> +-With--leak-check=full,"definitelylost"and"possiblylost"<br> +leaksarenowconsideredaspropererrors,ie.theyarecounted<br> +forthe"ERRORSUMMARY"andaffectthebehaviourof<br> +--error-exitcode.Theseleaksarenotcountedaserrorsif<br> +--leak-check=summaryisspecified,however.<br> +<br> +-Documentationfortheleakcheckerhasbeenimproved.<br> +<br> +<br> +*VariousaspectsofValgrind'stextoutputhavechanged.<br> +<br> +-Valgrind'sstart-upmessagehaschanged.Itisshorterbutalso<br> +includesthecommandbeingrun,whichmakesiteasiertouse<br> +--trace-children=yes.Anexample:<br> +<br> +-Valgrind'sshut-downmessageshavealsochanged.Thisismost<br> +noticeablewithMemcheck,wheretheleaksummarynowoccursbefore<br> +theerrorsummary.Thischangewasnecessarytoallowleakstobe<br> +countedaspropererrors(seethedescriptionoftheleakchecker<br> +changesaboveformoredetails).Thiswasalsonecessarytofixa<br> +longstandingbuginwhichusesofsuppressionsagainstleakswere<br> +not"counted",leadingtodifficultiesinmaintainingsuppression<br> +files(XXXXbugnumber).<br> +<br> +-Behaviorof-vhaschanged.Inpreviousversions,-vprintedout<br> +amixtureofmarginally-user-usefulinformation,andtool/core<br> +statistics.Thestatisticsprintinghasnowbeenmovedtoitsown<br> +flag,--stats=yes.Thismeans-vislessverboseandmorelikely<br> +toconveyusefulend-userinformation.<br> +<br> +-Theformatofsome(non-XML)stacktraceentrieshaschangeda<br> +little.Previouslythereweresixpossibleforms:<br> +<br> +0x80483BF:really(a.c:20)<br> +0x80483BF:really(in/foo/a.out)<br> +0x80483BF:really<br> +0x80483BF:(within/foo/a.out)<br> +0x80483BF:???(a.c:20)<br> +0x80483BF:???<br> +<br> +Thethirdandfourthoftheseformshavebeenmademoreconsistent<br> +withtheothers.Thesixpossibleformsarenow:<br> +<br> +0x80483BF:really(a.c:20)<br> +0x80483BF:really(in/foo/a.out)<br> +0x80483BF:really(in???)<br> +0x80483BF:???(in/foo/a.out)<br> +0x80483BF:???(a.c:20)<br> +0x80483BF:???<br> +<br> +Stacktracesproducedwhen--xml=yesisspecifiedaredifferent<br> +andunchanged.<br> +<br> +<br> +*HelgrindandPtrchecknowsupportXMLoutput,sotheycanbeused<br> +fromGUItools.Also,theXMLoutputmechanismhasbeen<br> +overhauled.<br> +<br> +-TheXMLformathasbeenoverhauledandgeneralised,soitismore<br> +suitableforerrorreportingtoolsingeneral.TheMemcheck<br> +specificaspectsofithavebeenremoved.Thenewformat,which<br> +isanevolutionoftheoldformat,isdescribedin<br> +docs/internals/xml-output-protocol4.txt.<br> +<br> +-Memcheckhasbeenupdatedtousethenewformat.<br> +<br> +-HelgrindandPtrcheckarenowabletoemitoutputinthisformat.<br> +<br> +-TheXMLoutputmechanismhasbeenoverhauled.XMLisnowoutput<br> +toitsownfiledescriptor,whichmeansthat:<br> +<br> +*ValgrindcanoutputtextandXMLindependently.<br> +<br> +*ThelongstandingproblemofXMLoutputbeingcorruptedby<br> +unexpectedun-taggedtextmessagesissolved.<br> +<br> +Asbefore,thedestinationfortextoutputisspecifiedusing<br> +--log-file=,--log-fd=or--log-socket=.<br> +<br> +Asbefore,XMLoutputforatoolisenabledusing--xml=yes.<br> +<br> +Becausethere'sanewXMLoutputchannel,theXMLoutput<br> +destinationisnowspecifiedby--xml-file=,--xml-fd=or<br> +--xml-socket=.<br> +<br> +Initialfeedbackhasshownthiscausessomeconfusion.To<br> +clarify,thetwoenvisagedusagescenariosare:<br> +<br> +(1)Normaltextoutput.Inthiscase,donotspecify--xml=yes<br> +noranyof--xml-file=,--xml-fd=or--xml-socket=.<br> +<br> +(2)XMLoutput.Inthiscase,specify--xml=yes,andoneof<br> +--xml-file=,--xml-fd=or--xml-socket=toselecttheXML<br> +destination,oneof--log-file=,--log-fd=or--log-socket=<br> +toselectthedestinationforanyremainingtextmessages,<br> +and,importantly,-q.<br> +<br> +-qmakesValgrindcompletelysilentonthetextchannel,<br> +exceptinthecaseofcriticalfailures,suchasValgrind<br> +itselfsegfaulting,orfailingtoreaddebugginginformation.<br> +Hence,inthisscenario,itsufficestocheckwhetherornot<br> +anyoutputappearedonthetextchannel.Ifyes,thenitis<br> +likelytobeacriticalerrorwhichshouldbebroughttothe<br> +attentionoftheuser.Ifno(thetextchannelproducedno<br> +output)thenitcanbeassumedthattherunwassuccessful.<br> +<br> +ThisallowsGUIstomakethecriticaldistinctiontheyneedto<br> +make(didtherunfailornot?)withouthavingtosearchor<br> +filterthetextoutputchannelinanyway.<br> +<br> +Itisalsorecommendedtouse--child-silent-after-fork=yesin<br> +scenario(2).<br> +<br> +<br> +*ImprovementsandchangesinHelgrind:<br> +<br> +-XMLoutput,asdescribedabove<br> +<br> +-Checksforconsistentassociationbetweenpthreadcondition<br> +variablesandtheirassociatedmutexesarenowperformed.<br> +<br> +-pthread_spinlockfunctionsaresupported.<br> +<br> +-Modestperformanceimprovements.<br> +<br> +-Initial(skeletal)supportfordescribingthebehaviourof<br> +non-POSIXsynchronisationobjectsthroughThreadSanitizer<br> +compatibleANNOTATE_*macros.<br> +<br> +-Morecontrollabletradeoffsbetweenperformanceandthelevelof<br> +detailof"previous"accessesinarace.Therearenowthree<br> +settings:<br> +<br> +*--history-level=full.Thisisthedefault,andwasalsothe<br> +defaultin3.4.x.Itshowsbothstacksinvolvedinarace,but<br> +requiresalotofmemoryandcanbeveryslowinprogramsthat<br> +domanyinter-threadsynchronisationevents.<br> +<br> +*--history-level=none.Thisonlyshowsthelaterstackinvolved<br> +inarace.Thiscanbemuchfasterthan--history-level=full,<br> +butmakesitmuchmoredifficulttofindtheotheraccess<br> +involvedintherace.<br> +<br> +Thenewintermediatesettingis<br> +<br> +*--history-level=approx<br> +<br> +Fortheearlier(other)access,twostacksarepresented.The<br> +earlieraccessisguaranteedtobesomewhereinbetweenthetwo<br> +programpointsdenotedbythosestacks.Thisisnotasuseful<br> +asshowingtheexactstackforthepreviousaccess(asper<br> +--history-level=full),butitisbetterthannothing,andit's<br> +almostasfastas--history-level=none.<br> +<br> +<br> +*NewfeaturesandimprovementsinDRD:<br> +<br> +-TheerrormessagesprintedbyDRDarenoweasiertointerpret.<br> +Insteadofusingtwodifferentnumberstoidentifyeachthread<br> +(ValgrindthreadIDandDRDthreadID),DRDdoesnowidentify<br> +threadsviaasinglenumber(theDRDthreadID).Furthermore<br> +"firstobservedat"informationisnowprintedforallerror<br> +messagesrelatedtosynchronizationobjects.<br> +<br> +-Addedsupportfornamedsemaphores(sem_open()andsem_close()).<br> +<br> +-Raceconditionsbetweenpthread_barrier_wait()and<br> +pthread_barrier_destroy()callsarenowreported.<br> +<br> +-Addedsupportforcustomallocatorsthroughthemacros<br> +VALGRIND_MALLOCLIKE_BLOCK()VALGRIND_FREELIKE_BLOCK()(definedin<br> +in<valgrind/valgrind.h>).Analternativeforthesetwomacrosis<br> +thenewclientrequestVG_USERREQ__DRD_CLEAN_MEMORY(definedin<br> +<valgrind/drd.h>).<br> +<br> +-Addedsupportforannotatingnon-POSIXsynchronizationobjects<br> +throughseveralnewANNOTATE_*()macros.<br> +<br> +-OpenMP:addedsupportfortheOpenMPruntime(libgomp)included<br> +withgccversions4.3.0and4.4.0.<br> +<br> +-Fasteroperation.<br> +<br> +-Addedtwonewcommand-lineoptions(--first-race-onlyand<br> +--segment-merging-interval).<br> +<br> +<br> +*Genuinelyatomicsupportforx86/amd64/ppcatomicinstructions<br> +<br> +Valgrindwillnowpreserve(memory-access)atomicityofLOCK-<br> +prefixedx86/amd64instructions,andanyothersimplyingaglobal<br> +buslock.DittoforPowerPCl{w,d}arx/st{w,d}cx.instructions.<br> +<br> +ThismeansthatValgrindedprocesseswill"playnicely"in<br> +situationswherecommunicationwithotherprocesses,orthekernel,<br> +isdonethroughsharedmemoryandcoordinatedwithsuchatomic<br> +instructions.Priortothischange,sucharrangementsusually<br> +resultedinhangs,racesorothersynchronisationfailures,because<br> +Valgrinddidnothonouratomicityofsuchinstructions.<br> +<br> +<br> +*Anewexperimentaltool,BBV,hasbeenadded.BBVgeneratesbasic<br> +blockvectorsforusewiththeSimPointanalysistool,whichallows<br> +aprogram'soverallbehaviourtobeapproximatedbyrunningonlya<br> +fractionofit.Thisisusefulforcomputerarchitecture<br> +researchers.YoucanrunBBVbyspecifying--tool=exp-bbv(the<br> +"exp-"prefixisshortfor"experimental").BBVwaswrittenby<br> +VinceWeaver.<br> +<br> +<br> +*ModestlyimprovedsupportforrunningWindowsapplicationsunder<br> +Wine.Inparticular,initialsupportforreadingWindows.PDBdebug<br> +informationhasbeenadded.<br> +<br> +<br> +*AnewMemcheckclientrequestVALGRIND_COUNT_LEAK_BLOCKShasbeen<br> +added.ItissimilartoVALGRIND_COUNT_LEAKSbutcountsblocks<br> +insteadofbytes.<br> +<br> +<br> +*TheValgrindclientrequestsVALGRIND_PRINTFand<br> +VALGRIND_PRINTF_BACKTRACEhavebeenchangedslightly.Previously,<br> +thestringwasalwaysprintedimmediatelyonitsownline.Now,the<br> +stringwillbeaddedtoabufferbutnotprinteduntilanewlineis<br> +encountered,orotherValgrindoutputisprinted(notethatfor<br> +VALGRIND_PRINTF_BACKTRACE,theback-traceitselfisconsidered<br> +"otherValgrindoutput").Thisallowsyoutousemultiple<br> +VALGRIND_PRINTFcallstobuildupasingleoutputline,andalsoto<br> +printmultipleoutputlineswithasinglerequest(byembedding<br> +multiplenewlinesinthestring).<br> +<br> +<br> +*ThegraphsdrawnbyMassif'sms_printprogramhavechangedslightly:<br> +<br> +-Thehalf-heightchars'.'and','arenolongerdrawn,because<br> +theyareconfusing.The--yoptioncanbeusedifthedefault<br> +y-resolutionisnothighenough.<br> +<br> +-Horizontallinesarenowdrawnafterthetopofasnapshotif<br> +thereisagapuntilthenextsnapshot.Thismakesitclearthat<br> +thememoryusagehasnotdroppedtozerobetweensnapshots.<br> +<br> +<br> +*Somethingthathappenedin3.4.0,butwasn'tclearlyannounced:the<br> +option--read-var-info=yescanbeusedbysometools(Memcheck,<br> +HelgrindandDRD).Whenenabled,itcausesValgrindtoreadDWARF3<br> +variabletypeandlocationinformation.Thismakesthosetools<br> +startupmoreslowlyandincreasesmemoryconsumption,but<br> +descriptionsofdataaddressesinerrormessagesbecomemore<br> +detailed.<br> +<br> +<br> +*exp-Omega,anexperimentalinstantaneousleak-detectingtool,was<br> +disabledin3.4.0duetoalackofinterestandmaintenance,<br> +althoughthesourcecodewasstillinthedistribution.Thesource<br> +codehasnowbeenremovedfromthedistribution.Foranyone<br> +interested,theremovaloccurredinSVNrevisionr10247.<br> +<br> +<br> +*Somechangeshavebeenmadetothebuildsystem.<br> +<br> +-VEX/isnowintegratedproperlyintothebuildsystem.Thismeans<br> +thatdependencytrackingwithinVEX/nowworksproperly,"make<br> +install"willworkwithoutrequiring"make"beforeit,and<br> +parallelbuilds(ie.'make-j')nowwork(previouslya<br> +.NOTPARALLELdirectivewasusedtoserializebuilds,ie.'make-j'<br> +waseffectivelyignored).<br> +<br> +-The--with-vexconfigureoptionhasbeenremoved.Itwasof<br> +littleuseandremovingitsimplifiedthebuildsystem.<br> +<br> +-Thelocationofsomeinstallfileshaschanged.Thisshouldnot<br> +affectmostusers.Thosewhomightbeaffected:<br> +<br> +*ForpeoplewhouseValgrindwithMPIprograms,theinstalled<br> +libmpiwrap.solibraryhasmovedfrom<br> +$(INSTALL)/<platform>/libmpiwrap.soto<br> +$(INSTALL)/libmpiwrap-<platform>.so.<br> +<br> +*ForpeoplewhodistributestandaloneValgrindtools,the<br> +installedlibrariessuchas$(INSTALL)/<platform>/libcoregrind.a<br> +havemovedto$(INSTALL)/libcoregrind-<platform>.a.<br> +<br> +Thesechangessimplifythebuildsystem.<br> +<br> +-Previously,allthedistributedsuppression(*.supp)fileswere<br> +installed.Now,onlydefault.suppisinstalled.Thisshouldnot<br> +affectusersastheotherinstalledsuppressionfileswerenot<br> +read;thefactthattheywereinstalledwasamistake.<br> +<br> +<br> +*KNOWNLIMITATIONS:<br> +<br> +-MemcheckisunusablewiththeIntelcompilersuiteversion11.1,<br> +whenitgeneratescodeforSSE2-and-abovecapabletargets.This<br> +isbecauseoficc'suseofhighlyoptimisedinlinedstrlen<br> +implementations.ItcausesMemchecktoreporthugenumbersof<br> +falseerrorseveninsimpleprograms.HelgrindandDRDmayalso<br> +haveproblems.<br> +<br> +Versions11.0andearliermaybeOK,butthishasnotbeen<br> +properlytested.<br> +<br> +<br> +Thefollowingbugshavebeenfixedorresolved.Notethat"n-i-bz"<br> +standsfor"notinbugzilla"--thatis,abugthatwasreportedtous<br> +butnevergotabugzillaentry.Weencourageyoutofilebugsin<br> +bugzilla(http://bugs.kde.org/enter_valgrind_bug.cgi)ratherthan<br> +mailingthedevelopers(ormailinglists)directly--bugsthatare<br> +notenteredintobugzillatendtogetforgottenaboutorignored.<br> +<br> +Toseedetailsofagivenbug,visit<br> +https://bugs.kde.org/show_bug.cgi?id=XXXXXX<br> +whereXXXXXXisthebugnumberaslistedbelow.<br> +<br> +84303HowaboutaLockChecktool?<br> +91633dereferenceofnullptrinvgPlain_st_basetype<br> +97452Valgrinddoesn'treportanypthreadsproblems<br> +100628leak-checkgetsassertionfailurewhenusing<br> +VALGRIND_MALLOCLIKE_BLOCKonmalloc()edmemory<br> +108528NPTLpthreadcleanuphandlersnotcalled<br> +110126Valgrind2.4.1configure.intramplesCFLAGS<br> +110128mallinfoisnotimplemented...<br> +110770VEX:Generatedfilesnotalwaysupdatedwhenmakingvalgrind<br> +111102Memcheck:problemswithlarge(memoryfootprint)applications<br> +115673Vex'sdecodershouldneverassert<br> +117564Falsepositive:Syscallparamclone(child_tidptr)contains<br> +uninitialisedbyte(s)<br> +119404executingsshfrominsidevalgrindfails<br> +133679Callgrinddoesnotwritepathnamestosourceswithdwarfdebug<br> +info<br> +135847configure.inproblemwithnongnucompilers(andpossiblefix)<br> +136154threads.c:273(vgCallgrind_post_signal):Assertion<br> +'*(vgCallgrind_current_fn_stack.top)==0'failed.<br> +136230memcheckreports"possiblylost",shouldbe"stillreachable"<br> +137073NULLargtoMALLOCLIKE_BLOCKcausescrash<br> +137904ValgrindreportsamemoryleakwhenusingPOSIXthreads,<br> +whileitshouldn't<br> +139076valgrindVT_GETSTATEerror<br> +142228complaintofelf_dynamic_do_relaintrivialusage<br> +145347spuriouswarningwithUSBDEVFS_REAPURB<br> +148441(wine)can'tfindmemoryleakinWine,win32binary<br> +executablefile.<br> +148742Leak-checkfailsassertonexit<br> +149878add(proper)checkforcallocintegeroverflow<br> +150606Callgraphisbrokenwhenusingcallgrindcontrol<br> +152393leakerrorsproduceanexitcodeof0.Ineedsomewayto<br> +causeleakerrorstoresultinanonzeroexitcode.<br> +157154documentation(leak-resolutiondocspeaksaboutnum-callers<br> +def=4)+whatisalossrecord<br> +159501incorrecthandlingofALSAioctls<br> +162020Valgrindinganempty/zero-bytefilecrashesvalgrind<br> +162482ppc:Valgrindcrasheswhilereadingstabsinformation<br> +162718x86:avoidsegmentselector0insys_set_thread_area()<br> +163253(wine)canonicaliseSymtabforgotsomefieldsinDiSym<br> +163560VEX/test_main.cismissingfromvalgrind-3.3.1<br> +164353malloc_usable_size()doesn'treturnausablesize<br> +165468Inconsistentformattinginmemcheckmanual--pleasefix<br> +169505main.c:286(endOfInstr):<br> +Assertion'ii->cost_offset==*cost_offset'failed<br> +177206Generatedefault.suppduringcompileinsteadofconfigure<br> +177209Configurevalt_load_addressbasedonarch+os<br> +177305eventfd/syscall323patchlost<br> +179731Testsfailtobuildbecauseofinliningofnon-localasmlabels<br> +181394helgrind:libhb_core.c:3762(msm_write):Assertion<br> +'ordxx==POrd_EQ||ordxx==POrd_LT'failed.<br> +181594Boguswarningforemptytextsegment<br> +181707dwarfdoesn'trequireenumerationstohavename<br> +185038exp-ptrcheck:"unhandledsyscall:285"(fallocate)onx86_64<br> +185050exp-ptrcheck:sg_main.c:727(add_block_to_GlobalTree):<br> +Assertion'!already_present'failed.<br> +185359exp-ptrcheck:unhandledsyscallgetresuid()<br> +185794"WARNING:unhandledsyscall:285"(fallocate)onx86_64<br> +185816Valgrindisunabletohandledebuginfoforfileswithsplit<br> +debuginfothatareprelinkedafterwards<br> +185980[darwin]unhandledsyscall:sem_open<br> +186238bbToIR_AMD64:disInstrmiscalculatednext%rip<br> +186507exp-ptrcheckunhandledsyscallsprctl,etc.<br> +186790Suppressionpatternusedforleaksarenotreported<br> +186796Symbolswithlength>200insuppressionfilesareignored<br> +187048drd:mutexPTHREAD_PROCESS_SHAREDattributemissinterpretation<br> +187416exp-ptrcheck:supportfor__NR_{setregid,setreuid,setresuid}<br> +188038helgrind:hg_main.c:926:mk_SHVAL_fail:the'impossible'happened<br> +188046bashismsintheconfigurescript<br> +188127amd64->IR:unhandledinstructionbytes:0xF00xF0xB00xA<br> +188161memcheck:--track-origins=yesasserts"mc_machine.c:672<br> +(get_otrack_shadow_offset_wrk):the'impossible'happened."<br> +188248helgrind:pthread_cleanup_push,pthread_rwlock_unlock,<br> +assertionfail"!lock->heldBy"<br> +188427Addsupportforepoll_create1(withpatch)<br> +188530SupportforSIOCGSTAMPNS<br> +188560Includevalgrind.specinthetarball<br> +188572ValgrindonMacshouldsuppresssetenv()memleak<br> +189054Valgrindfailstobuildbecauseofduplicatenon-localasmlabels<br> +189737vexamd64->IR:unhandledinstructionbytes:0xAC<br> +189762epoll_createsyscallnothandled(--tool=exp-ptrcheck)<br> +189763drdassertionfailure:s_threadinfo[tid].is_recording<br> +190219unhandledsyscall:328(x86-linux)<br> +190391dupof181394;seeabove<br> +190429Valgrindreportslotsoferrorsinld.sowithx86_642.9.90glibc<br> +190820Nodebuginformationonpowerpc-linux<br> +190820Nodebuginformationonpowerpc-linux<br> +191095PATCH:Improveusbdevfsioctlhandling<br> +191182memcheck:VALGRIND_LEAK_CHECKquadraticwhenbignrofchunks<br> +orbignroferrors<br> +191189--xml=yesshouldobey--gen-suppressions=all<br> +191192syslog()needsasuppressiononmacosx<br> +191271DARWIN:WARNING:unhandledsyscall:33554697a.k.a.:265<br> +191761getrlimitonMacOSX<br> +191992multiple--fn-skiponlyworkssometimes;dependentonorder<br> +192634V.reports"aspacemsync_check_mapping_callback:<br> +segmentmismatch"onDarwin<br> +192954__extension__missingon2clientrequests<br> +194429Crashatstart-upwithglibc-2.10.1andlinux-2.6.29<br> +194474"INSTALL"filehasdifferentbuildinstructionsthan"README"<br> +194671Unhandledsyscall(sem_wait?)frommacvalgrind<br> +195069memcheck:reportsleak(memorystillreachable)for<br> +printf("%d',x)<br> +195169drd:(vgDrd_barrier_post_wait):<br> +Assertion'r->sg[p->post_iteration]'failed.<br> +195268valgrind--log-filedoesn'taccept~/...<br> +195838VEXabort:LibVEX_N_SPILL_BYTEStoosmallforCPUIDboilerplate<br> +195860WARNING:unhandledsyscall:unix:223<br> +196528needaerrorsuppressionforpthread_rwlock_initunderosx?<br> +197227Supportaio_*syscallsonDarwin<br> +197456valgrindshouldreject--suppressions=(directory)<br> +197512DWARF2CFIreader:unhandledCFIinstruction0:10<br> +197591unhandledsyscall27(mincore)<br> +197793MergeDCASbranchtothetrunk==85756,142103<br> +197794AvoidduplicatefilenamesinVex<br> +197898makecheckfailsoncurrentSVN<br> +197901makecheckfailsalsounderexp-ptrcheckincurrentSVN<br> +197929Make--leak-resolution=highthedefault<br> +197930Reducespacingbetweenleakreports<br> +197933Printcommandlineofclientatstart-up,andshortenpreamble<br> +197966unhandledsyscall205(x86-linux,--tool=exp-ptrcheck)<br> +198395addBBVtothedistributionasanexperimentaltool<br> +198624MissingsyscallsonDarwin:82,167,281,347<br> +198649callgrind_annotatedoesn'tcumulatecounters<br> +199338callgrind_annotatesorting/thresholdsarebrokenforallbutIr<br> +199977Valgrindcomplainsaboutanunrecognizedinstructioninthe<br> +atomic_incstestprogram<br> +200029valgrindisn'tabletoreadFedora12debuginfo<br> +200760darwinunhandledsyscall:unix:284<br> +200827DRDdoesn'tworkonMacOSX<br> +200990VG_(read_millisecond_timer)()doesnotworkcorrectly<br> +201016Valgrinddoesnotsupportpthread_kill()onMacOS<br> +201169Document--read-var-info<br> +201323Pre-3.5.0performancesanitychecking<br> +201384Reviewusermanualforthe3.5.0release<br> +201585mfpvrnotimplementedonppc<br> +201708testsfailingbecausex86directionflagisleftset<br> +201757Valgrinddoesn'thandleanyrecentsys_futexadditions<br> +20437764-bitvalgrindcannotstartashellscript<br> +(with#!/path/to/shell)iftheshellisa32-bitexecutable<br> +n-i-bzdrd:fixedassertionfailuretriggeredbymutexreinitialization.<br> +n-i-bzdrd:fixedabugthatcausedincorrectmessagestobeprinted<br> +aboutmemoryallocationeventswithmemoryaccesstracingenabled<br> +n-i-bzdrd:fixedamemoryleaktriggeredbyvectorclockdeallocation<br> +<br> +(3.5.0:20Aug2009,vexr1913,valgrindr10846).<br> +<br> +<br> +<br> Release3.4.1(28February2009)<br> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br> 3.4.1isabug-fixreleasethatfixessomeregressionsandassertion<br> @@ -425,7 +991,7 @@ -Memcheckhasnewflags--malloc-fill=<hexnum>and<br> --free-fill=<hexnum>whichfreemalloc'd/free'dareaswiththe<br> specifiedbyte.Thiscanhelpshakeoutobscurememorycorruption<br> -problems.Thedefinednessandaddressibilityoftheseareasis<br> +problems.Thedefinednessandaddressabilityoftheseareasis<br> unchanged--onlythecontentsareaffected.<br> <br> -ThebehaviourofMemcheck'sclientrequestsVALGRIND_GET_VBITSand<br> @@ -2246,9 +2812,9 @@ <br><table class="nav" width="100%" cellspacing="3" cellpadding="2" border="0" summary="Navigation footer"> <tr> <td rowspan="2" width="40%" align="left"> -<a accesskey="p" href="dist.install.html"><<3.INSTALL</a></td> +<a accesskey="p" href="dist.authors.html"><<1.AUTHORS</a></td> <td width="20%" align="center"><a accesskey="u" href="dist.html">Up</a></td> -<td rowspan="2" width="40%" align="right"><a accesskey="n" href="dist.readme.html">5.README>></a> +<td rowspan="2" width="40%" align="right"><a accesskey="n" href="dist.readme.html">3.README>></a> </td> </tr> <tr><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td></tr> |