Octavio Alvarez wrote: > Well, Valgrind says "timer_create(evp)", not timerid and the problem > apparently relies *inside* eglibc.
Hmm... Regarding valgrind... The coreutils gets run through valgrind routinely. There are always lots of false positives. Often people report false positives to us and then they need to be triaged as such and explained. I know that people are trying to helpful by running popular programs through analysis tools but historically for the coreutils it hasn't been very helpful. > But anyway, that was not even the point. The point was that debugging > and bug reporting is difficult because there are no symbols to provide > complete backtraces to developers. Is there anyone that doesn't have the source code available? By the time I am geared to up to debug something in coreutils I always have the source code available and will use it for the debugging. I am not sure there will be much return on investment for the work to create and maintain a dbg package. Most of the coreutils programs simply interface with system calls. For most cases using strace on the program under question provides the needed information. There was another one of those just yesterday. And by the way... It would be nice if the original subject were maintained. With just a ping about a bug number it means everyone needs to go look up the bug number. It would be nicer if it the subject had told us coreutils-dbg as in the original report. Bob
signature.asc
Description: Digital signature
