c++ - Does stack unwinding really require locks? -


I am converting my code with mutrace and taking the following interesting / worrisome results:

  Mute X # 1260690 (0x0x7f87bc8eea40) is previously referenced by: /usr/lib/mutrace/libmutrace.so(pthread_mutex_lock+0x49) [0x7f87be0b76b9] /lib/x86_64-linux-gnu/libgcc_s.so.1(_Unwind_Find_FDE + 0x26) [0x7f87bc6eb0e6] mutrace: Showing 10 Most Compatibility Mutes: Mutes # Locked Cunt Cunt. Tot.Time [MS] avg.Time [ms] max.Time [MS] flag 1260690 19066789 150 9 831 109753 3600.883 0.000 0.226 M -..--.   

_Unwind_Find_FDE has to deal with stack unilining.

My application is multi-threaded with very strict latency requirements and so I want to finish it as easily as possible. Can a compiler or environmental settings be used to get rid of this function call without having to rewrite my code? We use exceptions for part of the flow control (probably inadvertently), but there will be a major refactoring job to fix this.

  G ++ (Ubuntu 4.8.2-19 Buntu 1) 4.8.2     

Stop using exceptions if you need less latency.

Comments

Popular posts from this blog

php - PDO bindParam() fatal error -

logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

java - Why my included JSP file won't get processed correctly? -