From: Melchior F. <mf...@kd...> - 2003-07-07 09:21:01
|
* Julian Seward -- Sunday 06 July 2003 14:57: > As I remember, this patch > requires #including a new file into coregrind/vg_unsafe.h, and > I am pretty paranoid about doing that because in the past such > patches have caused compilation failures on some Linux distros > and not others. Well, that's of course a problem. But would it decide whether some Linux ioctl will be supported or not? ("We don't support new ioctls, if this means to include yet another Linux kernel header." ?) As of now, valgrind false-positively reports "use of uninitialized memory" and it took me hours to find out that the bug was actually in valgrind, not in FlightGear. (I could have found out faster, but my trust in valgrind was unlimited. ;-) It would be nice if others wouldn't have to repeat this experience. It's not for =me=, because I =do= have this fixed in my version. m. :-) |