|
From: Julian S. <js...@ac...> - 2013-07-02 08:17:32
|
On 06/07/2013 06:55 PM, Julian Seward wrote: > Using Valgrind on phones or embedded targets in general can be > difficult because of its requirement to have the debuginfo objects > available in target's filesystem. [...] As of r13440 this is merged into trunk. For "normal" use of V on desktop Linux or MacOS, there should be no visible change, apart from the absence of virtual memory spiking when reading debuginfo from large objects, and marginally slower debuginfo reading (you'd have to look hard to see that, though.) Dwarf1 reading has been disabled and there doesn't seem to be much demand to reinstate it. Stabs reading also no longer works. I did look into making this work again, and it is doable, but I concluded that I did not have enough test cases to do it properly. If anyone wants stabs reading to work again, I am happy to fix it, provided you can supply a set of test cases (.so's) using stabs and (importantly) the "extension line" feature of stabs, which is the most complex part. Also the PDB reader doesn't work any more. The same comments re test cases apply -- or I am happy to give guidance to anyone wanting to fix it up. This has been a huge amount of hassle, but the upside is that debuginfo reading is now decoupled from the idea of mmaping files in. So it is more flexible. Also, range checking on the read data is much better: as far as I can tell, it is now impossible to segfault V by feeding it corrupted ELF or Dwarf information. J |