Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 Jun 2023 15:58:30 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 166921] Use after free in dtrace(1) error handling
Message-ID:  <bug-166921-227-kyPmAjVBIS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-166921-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-166921-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166921

Mark Johnston <markj@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |markj@FreeBSD.org
         Resolution|---                         |Unable to Reproduce
             Status|Open                        |Closed

--- Comment #4 from Mark Johnston <markj@FreeBSD.org> ---
I tried running "valgrind --tool=3Dmemcheck dtrace -n
'pid$target:libc*:mallc:entry' -c /bin/cat" and don't see any segfaults or
use-after-free reports.  (Valgrind is in much better shape now than it used=
 to
be.)  Since this report is quite old and we don't have any known stability
problems, let's close it.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-166921-227-kyPmAjVBIS>