[Fwd: Re: [Valgrind-users] OT: kcachegrind source annotation on .so]

[<jp...@mu...>]

---------------------------- Original Message ----------------------------
Subject: Re: [Valgrind-users] OT: kcachegrind source annotation on .so
From:
Date:    Mon, April 18, 2005 2:48 am
To:      val...@li...
--------------------------------------------------------------------------

That didn't help, but I was able to get them to show up by explicitly
adding every plugin that might possibly get loaded to the main
executable's link line (then they're not exactly acting as extensability
plugins, though).

-- 
  _
 ( \      _  \    /_ /  _ _  Jason Weber                  Glendale, CA
  \|(\/)()))  \/\/(-/_)(-/(  http://www.imonk.com/baboon  ba...@im...
//                                                      we...@ac...
 (/


On Mon, Apr 18, 2005 at 09:15:14AM +0200, Igmar Palsenberg wrote:
>
> <snip>
>
> > It all works on the primary executable, but our architecture is very
heavily plugin-based (dlopen, dlsym).
>
> <snip>
>
> > kcachegrind says "no source available for" and "no debug information
present" for the .so filename.  I specified all the source directories
explicitly in the 'Configure kcachgrind' GUI under (always).
>
> Don't do a dlclose() on the plugins, as that will remove them from
address  space, and prevents VG from doing lookups. Usually this can be
easely done  using #ifdef's, or with the VG runtime macros.
>
>
> Regards,
>
>
> 	Igmar
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users