Date: Wed, 22 Jun 2005 11:33:08 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@FreeBSD.org> Cc: sobomax@FreeBSD.org, current@FreeBSD.org, freebsd-amd64@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: Fatal trap 12 in exec_copyout_strings() Message-ID: <17081.33972.316494.40649@grasshopper.cs.duke.edu> In-Reply-To: <200506221031.55875.jhb@FreeBSD.org> References: <20050510223636.GA49927@xor.obsecurity.org> <200506171434.49008.jhb@FreeBSD.org> <17080.29141.918333.170950@grasshopper.cs.duke.edu> <200506221031.55875.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin writes: > > I think I figured it out. sobomax@ changed how much memory exec_copyin_args() > and exec_free_args() allocated and freed without updating > freebsd32_exec_copyin_args() and linux_exec_copyin_args(), so more memory was > freed than was allocated which would free memory out from other execs. Patch > is below. Let me know if it fixes the problem. > This works for me. Previously, running the cross compiler would panic the box instantly. Now it works fine. Your theory about freeing things from other execs makes sense because gcc is always exec'ing off different stages of the compilation.. Nice work! Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17081.33972.316494.40649>