Stack trace of blocking code

[medikoo]

I'm not sure whether that is possible, but it would be great to know, where application got blocked.

Currently we just know that process has blocked and tripwire aborts it, that works great. Still we miss information about execution stack trace that lead to block (most likely some infinite loop) and that's crucial information in most cases.

Providing stack trace with an error would be very very welcome

[tjanczuk]

I agree it would be a very valuable piece of information, but I was unable to find a way to extract it at the time the tripwire is activated without making changes in the node core. If anyone knows a way, speak up please.

---

From: Mariusz Nowak [[email protected]]
Sent: Wednesday, September 12, 2012 2:28 AM
To: tjanczuk/tripwire
Subject: [tripwire] Stack trace of blocking code (#1)

I'm not sure whether that is possible, but it would be great to know, where application got blocked.

Currently we just know that process has blocked and tripwire aborts it, that works great. Still we miss information about execution stack trace that lead to block (most likely some infinite loop) and that's crucial information in most cases.

Providing stack trace with an error would be very very welcome

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1.

[medikoo]

@tjanczuk I contacted node.js team about that. I think they might be willing to help, if you provide them more details, on how do you imagine stack trace could be accessible, or where you got stuck.

I unfortunately have zero experience with C++, so can't really provide them any insight

[jezell]

https://github.com/nodejs/nodereport/blob/master/src/node_report.cc

Could NodeReport code be plugged in to provide this functionality?