Thank you for your report. A fix which resolves this problem is now in Git[1]. Version 0.7.0, which will include the fix, is nearing release.[2] I expect it will be released in tarball form sometime in November 2012. You'll then be able to find it on the ltrace file-release page.[3] But it may take months or years to get into Debian.[4]
For now, I recommend you do what Adam Dingle[5] recommends. Install and use an alternative tracing tool.[6] Adam suggests latrace[7] or strace[8]. ^ [1]. http://anonscm.debian.org/gitweb/?p=collab-maint/ltrace.git;a=blob;f=NEWS ^ [2]. http://lists.alioth.debian.org/pipermail/ltrace-devel/2012-October/000756.html ^ [3]. https://alioth.debian.org/frs/?group_id=30892 ^ [4]. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675607 ^ [5]. http://lists.yorba.org/pipermail/shotwell/2012-April/003824.html ^ [6]. http://en.wikipedia.org/wiki/Ltrace#See_also ^ [7]. http://packages.debian.org/latrace ^ [8]. http://packages.debian.org/search?keywords=strace&searchon=names&exact=1 -- Jason Spiro: software/web developer/packager/trainer. Cellphone/IT consultant. I support Linux, UNIX, Windows, and more. Contact me to discuss your needs. Also ask me how I can reduce your phone and long-distance bills. +1 (416) 992-3445 / <http://www.jspiro.com/>. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
