daily CVS update output

2021-06-05 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/tests/mi P src/external/gpl3/gcc/lib/libbacktrace/arch/mipsn64el/config.h P src/external/gpl3/gcc/lib/libstdc++-v3/arch/mipsn64el/c++config.h P src/external/gpl3/gcc/lib/libstdc++-v3/arch/mipsn64el/symver-config.h P

Automated report: NetBSD-current/i386 build success

2021-06-05 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2021.06.05.22.17.15 blymn src/distrib/sets/lists/tests/mi,v 1.1055 2021.06.05.22.21.15 pgoyette src/sys/dev/mii/mii_verbose.c,v 1.7

Re: dump/restore out of range inode

2021-06-05 Thread J. Hannken-Illjes
Patrick, please try the attached diff so the "spcl.c_addr" test no longer runs off the spcl record. "blks" is used for multi-tape checkpointing and examining TS_INODE/TS_ADDR records should be sufficient as the are the only records that support holes in data. -- J. Hannken-Illjes -

Re: dump/restore out of range inode

2021-06-05 Thread J. Hannken-Illjes
> On 5. Jun 2021, at 12:31, Patrick Welche wrote: > > On Sat, Jun 05, 2021 at 10:03:21AM -, Michael van Elst wrote: >> pr...@cam.ac.uk (Patrick Welche) writes: >> >>> How can gdb not see a spcl anywhere? >> >> /usr/include/protocols/dumprestore.h:#define spcl u_spcl.s_spcl >> >> spcl is

Re: dump/restore out of range inode

2021-06-05 Thread Patrick Welche
On Sat, Jun 05, 2021 at 10:03:21AM -, Michael van Elst wrote: > pr...@cam.ac.uk (Patrick Welche) writes: > > >How can gdb not see a spcl anywhere? > > /usr/include/protocols/dumprestore.h:#define spcl u_spcl.s_spcl > > spcl is just a define that got resolved by the compiler. ach... here it

Re: dump/restore out of range inode

2021-06-05 Thread Michael van Elst
pr...@cam.ac.uk (Patrick Welche) writes: >How can gdb not see a spcl anywhere? /usr/include/protocols/dumprestore.h:#define spcl u_spcl.s_spcl spcl is just a define that got resolved by the compiler.

Re: dump/restore out of range inode

2021-06-05 Thread Patrick Welche
On Thu, Jun 03, 2021 at 05:14:07PM -, Michael van Elst wrote: > pr...@cam.ac.uk (Patrick Welche) writes: > > > DUMP: Child 29322 returns LOB status 213 > >213=0xd5 > > That's octal. Return status 0213 = 139 -> WCOREFLAG(==128) + signal 11. > > >Can this happen if the original filesystem is

Automated report: NetBSD-current/i386 build failure

2021-06-05 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2021.06.05.06.23.48. An extract from the build.sh output follows: === 1 extra files in DESTDIR =