Lines Matching full:that
10 IS> I would like to write a valgrind tool that uses the standard c
12 IS> happens to use stdlib). I noticed that all the tools link with -
21 RW> twice. There's no telling how libc would react to that.
23 Though I agree that the short answer is "sorry, that's not supported",
34 that are the reason Valgrind tools don't link with the standard
35 libraries. The most fundamental one is that Valgrind and glibc are
36 both designed with the assumption that they alone will be talking to
43 research tool I was working on did that for a while. However, we gave
44 that up because of a further issue that affects glibcs configured with
49 glibc functions before initializing this, it crashes. That's the point
57 So if you need C standard library functionality that isn't covered by
