Note: getpid() is also a syscall, so calling gettid() is no more expensive than
calling getpid(). The expensive part of the current trace implementation is the
file I/O.
Having said that, I agree that it could be useful to keep a database of the
threads and instead log e.g. the name of the thread. This will be more
expensive than just logging the Linux thread id, but it is portable and it will
make the trace output more readable.
---
** [tickets:#1622] base: Include thread id in trace when supported**
**Status:** unassigned
**Milestone:** 5.0.FC
**Created:** Mon Dec 07, 2015 08:45 AM UTC by Anders Widell
**Last Updated:** Mon Dec 07, 2015 08:45 AM UTC
**Owner:** nobody
Logging of thread id in trace files was removed in changeset 1676:29a0e85f7707
[29a0e8] since gettid() is not part of LSB. We could re-introduce this feature
by loading the gettid symbol dynamically. If the symbol is not avialable, we
can simply skip logging the thread id.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
