Re: Someone using COMPAT_SVR4(_32) ?
Jerome Ibanes <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.sparc64 |
|---|---|
| Message-ID | <CAB+41mFQvw=1eNJK0R0BQePr=98SXkk8pM=8yk13CnNxeKekhw@mail.gmail.com> |
Then it's likely that one of the changes between the 5 and 6 branches broke compat_svr4, other than going through each patch in arch/sparc64 and running a test on 6.0.x; which other option do you suggest to narrow this down? Jerome On Wed, Sep 13, 2017 at 11:06 AM, Martin Husemann <[email protected]> wrote: > On Wed, Sep 13, 2017 at 11:01:14AM +0200, Jerome Ibanes wrote: >> Martin, >> >> 6.0.6 sparc64, 6.1.5 sparc64, 7.1 sparc64 (all GENERIC), fail with the same >> behavior (meaning, same ktrace ouput) given the same payload (sparc >> solaris 2.6), ktrace shows: > > OK, 7.1 definitively has the fix I was thinking about, so this is something > else. > > Martin