Displaying 3 results from an estimated 3 matches for "ldpreload".
Did you mean:
ld_preload
2011 Nov 11
0
[LLVMdev] google heap profile
...d.org/docs/manual/ms-manual.html
>
> I've been using valgrind too. It seems to work fine.
>
> I need to independently validate some numbers though because the answer
> has big implications for some planning we are doing.
>
In the past I have use the Google perf tools by using LDPRELOAD to inject
them into the running binary.
Note that the subprocess-ing can impact things, you need to drop down to
the cc1 invocation first.
Still, I have found that the heap profiling in these tools is strictly
inferior to massif. I'd trust it. There are lots of flags you can give to
massif to...
2011 Nov 11
2
[LLVMdev] google heap profile
On 11/11/2011 11:39 AM, Chandler Carruth wrote:
> On Fri, Nov 11, 2011 at 11:36 AM, reed kotler <rkotler at mips.com
> <mailto:rkotler at mips.com>> wrote:
>
> Is anybody using the google heap profiler to analyze clang/llvm ??
>
> http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html
>
> If so, do you know how to modify the build
1997 Jul 17
0
KSR[T] Advisory #2: ld.so
...if (!argv0 && !(argv0 = getenv(LDD_ARGV0)))
argv0 = LDSO_IMAGE;
-
+ argv0=argv_remap(argv0);
+
/* hmm, you want your own configuration, do you? */
if (getuid() == geteuid() && getgid() == getegid())
{
@@ -328,6 +371,11 @@
.text section. This is passed to ldpreload() below */
if (preload || callback)
{
+ if(nlibs==11)
+ {
+ fdprintf(2, "%s: too many preloads\n",argv[0]);
+ exit(EXIT_FATAL);
+ }
libs[nlibs] = alloca(strlen(buffer)+1);
strcpy(libs[nlibs], buffer);
nlibs++;
---- cut h...