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
F138024327: D14638.id40129.diff
Fri, Nov 28, 6:45 AM
Unknown Object (File)
Sun, Nov 9, 2:26 AM
Unknown Object (File)
Thu, Oct 30, 4:40 AM
Unknown Object (File)
Oct 13 2025, 4:01 AM
Unknown Object (File)
Oct 13 2025, 4:01 AM
Unknown Object (File)
Oct 12 2025, 4:13 PM
Unknown Object (File)
Oct 11 2025, 8:52 PM
Unknown Object (File)
Sep 17 2025, 3:03 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.