Re: Making sense of ktrace(1) output

Unfortunately I have to profile all of the source up the tree to
create profiled symbols, and I'm running into some issues profiling
liblegacy.
Does anyone have any hints for getting around that, or just
profiling all of the relevant libs?

I think you can build fbsd with profiling of all libraries (in base) and
run it like that...
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"