> On Jun 24, 2017, at 6:55 PM, David Wolfskill <da...@catwhisker.org> wrote: > > On Sat, Jun 24, 2017 at 06:48:03PM -0700, Manfred Antar wrote: >> ... >>> ktrace your failing ruby invocation, then post output of kdump -H somewhere. >>> >> >> Ok not sure if this is right , but this is what i did: >> >> (tmp)4637}ktrace /usr/local/bin/ruby -v > > You might want to re-do that, specifying the "-di" flags to ktrace (if > the output fails to include activities from child processes, and tracing > those is of interest).
Ok did: ktrace -di /usr/local/bin/ruby -v kdump -H -f ./ktrace.out >kdump-new.txt File is at : http://www.pozo.com/kernel/kdump-new.txt <http://www.pozo.com/kernel/kdump-new.txt> smaller than the first one. Manfred -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
