Re: bin/52302 (sh segfault)

To: kre%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, kre%NetBSD.org@localhost, coypu%sdf.org@localhost
Subject: Re: bin/52302 (sh segfault)
From: kre%NetBSD.org@localhost
Date: Thu, 15 Jun 2017 20:55:08 +0000 (UTC)

Synopsis: sh segfault

Responsible-Changed-From-To: bin-bug-people->kre
Responsible-Changed-By: kre%NetBSD.org@localhost
Responsible-Changed-When: Thu, 15 Jun 2017 20:55:08 +0000
Responsible-Changed-Why:
I am (for now) handling this PR


State-Changed-From-To: open->analyzed
State-Changed-By: kre%NetBSD.org@localhost
State-Changed-When: Thu, 15 Jun 2017 20:55:08 +0000
State-Changed-Why:
I believe I have already fix this one in my (uncommitted) sources.
There are a number of internal mem management weirdnesses I have
been encountering.

But it would help if you cound send me the script that caused it
so I could verify (private e-mail is fine.)

kre

Prev by Date: NetBSD Nightly Trouble Ticket Report
Next by Date: Re: bin/52302: sh segfault
Previous by Thread: bin/52302: sh segfault
Next by Thread: Re: bin/52302 (sh segfault)
Indexes:

Home | Main Index | Thread Index | Old Index