Compilations errors with plan9port on 2018/04/05 snapshot

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
Output of compiling plan9port on amd64 with the april 5 snaphot

===> plan9port-20180117 depends on: bzip2-* -> bzip2-1.0.6p8
===>  Verifying specs:  X11 Xext c m pthread util fontconfig freetype z
===>  found X11.16.1 Xext.13.0 c.92.3 m.10.1 pthread.25.1 util.13.0
fontconfig.11.0 freetype.28.2 z.5.0
===>  Checking files for plan9port-20180117
>> Fetch
>> https://github.com/9fans/plan9port/archive/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz
>> Fetch http://pdos.lcs.mit.edu/~rsc/pgw.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/pgw.tar.bz2
pgw.tar.bz2  100%
|***********************************************************************************************************|
9184 KB    00:11
>> Fetch http://pdos.lcs.mit.edu/~rsc/software/plan9/roget.tar.bz2
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/roget.tar.bz2
roget.tar.bz2 100%
|**********************************************************************************************************|
471 KB    00:01
>> Fetch http://pdos.lcs.mit.edu/~rsc/scat.tgz
ftp: SSL write error: name `pdos.lcs.mit.edu' not present in server
certificate
>> Fetch
>> https://ftp.openbsd.org/pub/OpenBSD/distfiles/plan9port/scat.tgz
scat.tgz     100%
|***********************************************************************************************************|
5024 KB    00:09
>> (SHA256) plan9port/019be4481fee53a999ccb73c78e40df5f408b24e.tar.gz:
>> OK
>> (SHA256) plan9port/pgw.tar.bz2: OK
>> (SHA256) plan9port/roget.tar.bz2: OK
>> (SHA256) plan9port/scat.tgz: OK
===>  Extracting for plan9port-20180117
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/pgw.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/dict
&& tar xjf /usr/ports/distfiles/plan9port/roget.tar.bz2
cd
/usr/obj/ports/plan9port-20180117/plan9port-019be4481fee53a999ccb73c78e40df5f408b24e/sky
&& tar xzf /usr/ports/distfiles/plan9port/scat.tgz
===>  Patching for plan9port-20180117
Segmentation fault (core dumped)
*** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
status (/usr/ports/infrastructure/mk/arch-defines.mk:12)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:45)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/arch-defines.mk:49)
*** Parse error: Malformed conditional (${PROPERTIES:Mclang})
(/usr/ports/infrastructure/mk/arch-defines.mk:52)
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/arch-defines.mk:52)
*** Parse error: Malformed conditional (${PROPERTIES:Mclang})
(/usr/ports/infrastructure/mk/bsd.port.mk:307)
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/bsd.port.mk:307)
*** Parse error: Malformed conditional (${PROPERTIES:Mgcc4})
(/usr/ports/infrastructure/mk/bsd.port.mk:309)
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/bsd.port.mk:309)
*** Parse error: Wrong number of items in for loop
(/usr/ports/infrastructure/mk/bsd.port.arch.mk:72)
1 items for 2 variables: amd64
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/bsd.port.arch.mk:72)
*** Parse error: Need an operator in 'endfor'
(/usr/ports/infrastructure/mk/bsd.port.arch.mk:80)
*** Parse error: Malformed conditional (${PROPERTIES:Mclang})
(/usr/ports/infrastructure/mk/bsd.port.mk:763)
*** Parse error: Missing dependency operator
(/usr/ports/infrastructure/mk/bsd.port.mk:763)
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2604
'/usr/obj/ports/plan9port-20180117/.patch_done')
*** Error 1 in /usr/ports/plan9/plan9port
(/usr/ports/infrastructure/mk/bsd.port.mk:2417 'build')
`

Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Philip Guenther-2
On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand <[hidden email]>
wrote:

> Output of compiling plan9port on amd64 with the april 5 snaphot
>
...

> ===>  Patching for plan9port-20180117
> Segmentation fault (core dumped)
> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
>

dmesg from this box, please.


Philip Guenther
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Philip Guenther-2
On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther <[hidden email]> wrote:

> On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand <[hidden email]
> > wrote:
>
>> Output of compiling plan9port on amd64 with the april 5 snaphot
>>
> ...
>
>> ===>  Patching for plan9port-20180117
>> Segmentation fault (core dumped)
>> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
>>
>
> dmesg from this box, please.
>

Also, does this segfault happen consistently at that same exact spot, or is
it inconsistent?
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
On 04/05, Philip Guenther wrote:

> On Thu, Apr 5, 2018 at 9:50 PM, Philip Guenther <[hidden email]> wrote:
>
> > On Thu, Apr 5, 2018 at 7:53 PM, Patrick Marchand <[hidden email]
> > > wrote:
> >
> >> Output of compiling plan9port on amd64 with the april 5 snaphot
> >>
> > ...
> >
> >> ===>  Patching for plan9port-20180117
> >> Segmentation fault (core dumped)
> >> *** Warning in /usr/ports/plan9/plan9port: "uname -m" returned non-zero
> >>
> >
> > dmesg from this box, please.
> >
>
> Also, does this segfault happen consistently at that same exact spot, or is
> it inconsistent?
It appears to be inconsistent, I've joined a file containing a few
failed runs and another with the dmesg.

dmesg.txt (8K) Download Attachment
errors.txt (81K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
Compilation succeeds on the april 8 snapshot

Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
On 04/08, Patrick Marchand wrote:
> Compilation succeeds on the april 8 snapshot

Though now I'm getting Abort Trap whenever I try to run the plumber or
acme. I was able to compile some programs with mk though, as I compiled
both $PLAN9/src/cmd/upas and $PLAN9/src/cmd/upas/nfs. I've joined the
dmesg of the current system.

dmesg.txt (28K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
In reply to this post by Patrick Marchand
On 04/08, Patrick Marchand wrote:
> Compilation succeeds on the april 8 snapshot
And heres the acme.core generated after acme abort trap.

acme.core (515K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Theo de Raadt-2
In reply to this post by Patrick Marchand
Patrick Marchand <[hidden email]> wrote:

> On 04/08, Patrick Marchand wrote:
> > Compilation succeeds on the april 8 snapshot
>
> Though now I'm getting Abort Trap whenever I try to run the plumber or
> acme. I was able to compile some programs with mk though, as I compiled
> both $PLAN9/src/cmd/upas and $PLAN9/src/cmd/upas/nfs. I've joined the
> dmesg of the current system.

From your mail:

trap pid 4946 tid 8385 type 6: sp 10581fac3000 not inside 7f7fffbcc000-7f7ffffcc000
trap pid 1024 tid 121465 type 6: sp 1e5a10690248 not inside 7f7fffbfb000-7f7fffffa000

At the moment snapshots contain the MAP_STACK diff.  Your program is
setting up threads incorrectly (it has it's own thread library?),
resulting in stacks not being mapped with MAP_STACK.  Stacks must be
carefully setup now.  ktrace -di may expose the memory allocation which
setup an address corresponding to a crash, basically a mmap with MAP_STACK
will be missing.

Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
On 04/08, Theo de Raadt wrote:
> At the moment snapshots contain the MAP_STACK diff.  Your program is
> setting up threads incorrectly (it has it's own thread library?),
> resulting in stacks not being mapped with MAP_STACK.  Stacks must be
> carefully setup now.  ktrace -di may expose the memory allocation which
> setup an address corresponding to a crash, basically a mmap with MAP_STACK
> will be missing.
So there is a mmap right before it crashes and it does not set
MAP_STACK, only MAP_PRIVATE|MAP_ANON. I dont exactly have the time to
investigate more today, but I'll look at it again later this week. In
the meantime I've joined the output of kdump.

kdump.text (97K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Gleydson Soares-2
Hi Patrick,
could you please test this diff?
https://marc.info/?l=openbsd-ports&m=152160090624047&w=2

Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Patrick Marchand
On 04/08, Gleydson Soares wrote:
> Hi Patrick,
> could you please test this diff?
> https://marc.info/?l=openbsd-ports&m=152160090624047&w=2

The diff worked, I was able to run plumber, factotum and acme without
any aborts.

Thanks!

Reply | Threaded
Open this post in threaded view
|

Re: Compilations errors with plan9port on 2018/04/05 snapshot

Gleydson Soares-2
On Sun, Apr 08, 2018 at 07:26:50PM -0400, Patrick Marchand wrote:
> On 04/08, Gleydson Soares wrote:
> > Hi Patrick,
> > could you please test this diff?
> > https://marc.info/?l=openbsd-ports&m=152160090624047&w=2
>
> The diff worked, I was able to run plumber, factotum and acme without
> any aborts.
>
> Thanks!

i've committed it.
thanks for testing,