Re: MALLOC_STATS: dump internal state and leak info via utrace(2)

On Sun, Apr 09, 2023 at 12:17:35PM +0200, Otto Moerbeek wrote: > On Sun, Apr 09, 2023 at 10:08:25AM +0200, Claudio Jeker wrote: > > > On Sun, Apr 09, 2023 at 09:15:12AM +0200, Otto Moerbeek wrote: > > > On Sun, Apr 09, 2023 at 08:20:43AM +0200, Otto Moerbeek wrote: > > > > > > > On Sun, Apr 09,

Re: cleanup vmm_start_vm, simplifying fd cleanup

Philip Guenther writes: > On Fri, Apr 7, 2023 at 9:44 AM Dave Voutila wrote: > ... > > Touch longer, but won't generate ktrace noise by blind calls to close(2) > and also accounts for the other error conditions (EINTR, EIO). > > For EIO, not sure yet how we want to handle it other than log

Re: patch: profiling using utrace(2) (compatible with pledge and unveil)

Sebastien Marie wrote: > For post-execution gmon.out extraction, an helper might be needed: ktrace.out > could contain multiple gmon.out files. kdump can be taught to generate the right file.

patch: profiling using utrace(2) (compatible with pledge and unveil)

Hi, After otto@ work on mallocdump using utrace(2), I started to look again at profiling (see moncontrol(2)). The current implementation tries to write a gmon.out file at program exit(3) time, which isn't compatible with pledge(2) or unveil(2). This diff changes the way the runtime profiling