Page MenuHomeFreeBSD

postmortem DTrace frequently broken under vmware
Needs ReviewPublic

Authored by sam_samgwydir.com on Mar 10 2018, 7:37 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, May 18, 1:50 AM
Unknown Object (File)
Tue, May 13, 11:26 PM
Unknown Object (File)
Apr 29 2025, 8:29 PM
Unknown Object (File)
Apr 24 2025, 3:45 AM
Unknown Object (File)
Mar 14 2025, 9:48 PM
Unknown Object (File)
Feb 22 2025, 11:59 PM
Unknown Object (File)
Dec 12 2024, 9:02 PM
Unknown Object (File)
Dec 3 2024, 6:02 PM

Details

Reviewers
gnn
Summary

Here is the bug ticket from illumos:
https://illumos.org/issues/9058

When debugging cores created with postmortem DTrace (http://dtrace.org/guide/chp-post.html) under VMWare fusion, mdb would often crash. It turned out a bug in how libdtrace consumed the tracing data stored inside the core.

Test Plan

Tested on SmartOS/illumos, used to debug the ongoing bhyve/illumos effort.

I need to re-create this problem on FreeBSD. I'll report back when that is done.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

Awesome! I've seen reports of this issue on FreeBSD but haven't reproduced it myself. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218452

I'll review this later this weekend.