Date: Mon, 27 Feb 2017 22:27:17 -0800 From: "Simon J. Gerraty" <sjg@juniper.net> To: Iblis Lin <iblis@hs.ntnu.edu.tw> Cc: <freebsd-current@freebsd.org>, <sjg@juniper.net> Subject: Re: bmake core dump Message-ID: <77715.1488263237@kaos.jnpr.net> In-Reply-To: <20170228034153.GC31394@abeing> References: <20170227101044.GB31394@abeing> <65586.1488222403@kaos.jnpr.net> <20170228034153.GC31394@abeing>
next in thread | previous in thread | raw e-mail | index | archive | help
Iblis Lin <iblis@hs.ntnu.edu.tw> wrote: > Accutally, I made it core dump via a julia script. > Please checkout this code I'm not familiar with juila, in most scripting languages cmd =3D `/usr/bin/make -f - -V MAKE_ENV` would run that command and assign the output to cmd. The make instance would be reading from stdin which is rather unknown at that point. Could you perhaps run that with ktrace? Eg. ktrace -i -t cnis -f /var/tmp/make.kt whatever command you ran kdump -m 128 -f /var/tmp/make.kt > /var/tmp/make.kd that would show what make is actually reading > =E2=94=94=E2=94=80[iblis@abeing ]% cat test.jl > makefile=3D""" > CATEGORIES=3D devel >=20 > USES=3D > .include <bsd.port.mk>""" >=20 > cmd =3D `/usr/bin/make -f - -V MAKE_ENV` > in_ =3D Pipe() > out, proc =3D open(cmd, "r", in_) >=20 > print(in_, makefile) > close(in_) >=20 > @assert success(proc) > close(out)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77715.1488263237>