You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Freshly updated sysdig 0.1.87 (Ubuntu 12.04) has just failed on me with what looks like memory corruption. Happened just once, not sure if reproducible, though subsequent sysdig runs seem fine (this is a production machine I really don't want to kill in the middle of the day if the kernel part does something weird too).
No core dump or other info, sorry. dmesg looks clean (no suspicious messages from sysdig).
Is this something that happens to you regularly?
I've recently done several fixes in that section of the code, so if you can replicate the issue, could you see if a build from master fixes it?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Freshly updated sysdig 0.1.87 (Ubuntu 12.04) has just failed on me with what looks like memory corruption. Happened just once, not sure if reproducible, though subsequent sysdig runs seem fine (this is a production machine I really don't want to kill in the middle of the day if the kernel part does something weird too).
No core dump or other info, sorry. dmesg looks clean (no suspicious messages from sysdig).
The text was updated successfully, but these errors were encountered: