If you have USDT probes in static functions, the dtrace -G invocation will generate these symbols. They be should be scoped local in the final binary (I'm surprised that they're showing up in the dynstr -- that's probably a bug in the linker).
Once the following bug is putback, it will be possible for DTrace to mark these temporary symbols so that they don't show up in the final binary at all: 6602451 new symbol visibilities required: EXPORTED, SINGLETON and ELIMINATE Adam On Tue, Oct 02, 2007 at 05:53:17PM -0700, Alexander Kolbasov wrote: > Hello, > > I was comparing two workspaces using wsdiff and noticed unexpected changes in > libc which looked like these: > > lib/libc.so.1 > NOTE: ELF .dynstr difference detected. > > 1427,1428c1427,1428 > < 0026220 t \0 $ d t r a c e 1 5 0 7 3 3 . > < 74002464 74726163 65313530 3733332e > --- > > 0026220 t \0 $ d t r a c e 1 4 9 4 2 0 . > > 74002464 74726163 65313439 3432302e > 1433,1434c1433,1434 > < 0026300 \0 $ d t r a c e 1 5 0 7 3 3 . m > < 00246474 72616365 31353037 33332e6d > --- > > 0026300 \0 $ d t r a c e 1 4 9 4 2 0 . m > > 00246474 72616365 31343934 32302e6d > 1439,1442c1439,1442 > < 0026360 u p _ a l l \0 $ d t r a c e 1 5 > < 75705f61 6c6c0024 64747261 63653135 > < 0026400 0 7 3 3 . m u t e x _ t r y l o > < 30373333 2e6d7574 65785f74 72796c6f > --- > > 0026360 u p _ a l l \0 $ d t r a c e 1 4 > > 75705f61 6c6c0024 64747261 63653134 > > 0026400 9 4 2 0 . m u t e x _ t r y l o > > 39343230 2e6d7574 65785f74 72796c6f > > ... > > What are these and why they can show up? > > - akolb > > > _______________________________________________ > dtrace-discuss mailing list > [email protected] -- Adam Leventhal, FishWorks http://blogs.sun.com/ahl _______________________________________________ dtrace-discuss mailing list [email protected]
