build.sh errors.

2014-05-22 Thread Ilia Zykov
I have a fresh installed system from autobuild. NetBSD 6.99.40 (GENERIC) #0: Tue May 6 04:20:54 UTC 2014 bui...@b2.netbsd.org:/home/builds/ab/HEAD/amd64/201405060250Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/GENERIC amd64 I am going to try this on i386. after: === build.sh command:

Re: build.sh errors.

2014-05-22 Thread Ilia Zykov
=== build.sh command:./build.sh -m amd64 -U -j8 -N0 -T ../amd64/B140522161139/tools -O ../amd64/B140522161139/obj tools === build.sh started:Thu May 22 16:11:39 MSK 2014 === NetBSD version: 6.99.42 === MACHINE: amd64 === MACHINE_ARCH:x86_64 === Build platform:

Re: build.sh errors.

2014-05-22 Thread Ilia Zykov
On the Linux cross compiled normal. [...] build.sh command:./build.sh -m amd64 -U -j8 -N0 -u -T ../amd64/B140522162251/tools -O ../amd64/B140522162251/obj release build.sh started:Thu May 22 16:37:28 MSK 2014 NetBSD version: 6.99.42 MACHINE:

buffer overflow, bad string handling in network lib?

2014-05-22 Thread B Harder
$ ftp ftp.freebsd.org login anonymous ftp ls screen fills w/ 'h' characters, repeating, presumably forever. I've also noticed this working/playing w/ another network library, but I assumed it was in my alpha code, or it's dependencies... I'll see if I can find more details, but thought I'd

Re: buffer overflow, bad string handling in network lib?

2014-05-22 Thread Martin Husemann
On Thu, May 22, 2014 at 11:47:38AM -0700, B Harder wrote: $ ftp ftp.freebsd.org login anonymous ftp ls screen fills w/ 'h' characters, repeating, presumably forever. FWIW: I can not reproduce it, but you might get connected to another server, I got to: Trying 2001:6c8:130:800::4:21 ...

Re: build.sh errors. Maybe serious BUG.

2014-05-22 Thread Ilia Zykov
On 22.05.2014 14:51, Ilia Zykov wrote: I have a fresh installed system from autobuild. NetBSD 6.99.40 (GENERIC) #0: Tue May 6 04:20:54 UTC 2014 bui...@b2.netbsd.org:/home/builds/ab/HEAD/amd64/201405060250Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/GENERIC amd64 I am going to try

Re: buffer overflow, bad string handling in network lib?

2014-05-22 Thread B Harder
Select ktrace output: [...] 2486 1 ftp GIO fd 1 wrote 5 bytes ftp 2486 1 ftp RET write 5 2486 1 ftp CALL ioctl(0,TIOCGETA,0x7f7ff7b1ca98) 2486 1 ftp GIO fd 0 read 44 bytes

Re: buffer overflow, bad string handling in network lib?

2014-05-22 Thread B Harder
Nevermind -- it looks like a stray entry in my .editrc. If it turns out it is a real issue, I'll repost. Apologies for the noise. -bch On 5/22/14, B Harder brad.har...@gmail.com wrote: Select ktrace output: [...] 2486 1 ftp GIO fd 1 wrote 5 bytes ftp 2486

Re: i386 DRMKMS results, 22 May 2014

2014-05-22 Thread John D. Baker
On Wed, 21 May 2014, Taylor R Campbell wrote: I re-enabled various DMI-based quirkarounds, including one for the 845 device you have. Can you update and try again? (That won't fix the problem that the kernel panics if the hardware is a little hosed, unfortunately.) Unfortunately, it broke

daily CVS update output

2014-05-22 Thread NetBSD source update
Updating src tree: P src/common/lib/libc/arch/x86_64/atomic/atomic.S P src/common/lib/libc/arch/x86_64/gen/byte_swap_2.S P src/common/lib/libc/arch/x86_64/gen/byte_swap_4.S P src/common/lib/libc/arch/x86_64/gen/byte_swap_8.S P src/common/lib/libc/arch/x86_64/string/memset.S P src/doc/3RDPARTY P