On 11/16/2012 01:46 PM, Wolfgang Denk wrote:
Dear Daniel Janzon,
In message <[email protected]> you wrote:
Did anyone ever succeed to run Valgrind on Eldk 4.2? It seems
to boil down to getting the debug version of glibc. Searching
the web and the mailing list archives, some people tried, did
anyone of you succeed?
Why exactly would you want to use the nearly 5 year old ELDK 4.2, when
recent versions such as 5.2.1 have this working out of the box?
I want to debug a memory leak in a legacy product. Updating to
a new eldk version seems like overkill for that, but maybe the
transition is smooth.
Blog post that I can't follow since I can't find the glibc source
package:
There is no separate glibc package. As explained before, what you are
asking for cannot be easily done in ELDK 4.x; for a detailed
explanation please see
http://article.gmane.org/gmane.comp.embedded.eldk/1877
I really recommend to update and use ELDK 5.x instead (either the
existing v5.2.1, or you wait a bit and jump onto the upcoming v5.3).
Ok, I will consider that. Thanks for your quick reply.
All the best,
Daniel
_______________________________________________
eldk mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/eldk
