KDL when configure bison-2.6.4

[diger]

hrev44732 gcc4, gcc4.6.3

When trying to configure the bison I get KDL

[diger]

KDL in vfs code. See screenshot for more details

[diver]

Might be a dupe of #1988.

[siarzhuk]

This test reproduces the behaviour:

#include <fcntl.h>

int
main ()
{
	int result = 0;
	static char const sym[] = "conftest.sym";
	if (symlink ("/dev/null", sym) != 0)
		result |= 2;
	else
	{
		int fd = 0;
		fd = open (sym, O_WRONLY | O_NOFOLLOW | O_CREAT, 0);
		if (fd >= 0)
		{
			close (fd);
			result |= 4;
		}
	}
	return result;
}

[diger]

This bug is reproduced when configuring gettext-runtime 0.18.2 & gettext-tools 0.18.2

[anevilyak]

Replying to siarzhuk:

This test reproduces the behaviour:

Hi Siarzhuk,

I don't suppose there's anything special about your and/or diger's system configuration? Thus far neither the above test nor any of the configure scripts mentioned are reproducing the panic over here. As a first hunch I tried switching to a cyrillic locale but that made no difference. hrev45350, gcc4, 8GB of RAM and 8 CPU cores over here for reference.

[siarzhuk]

Replying to anevilyak:

I don't suppose there's anything special about your and/or diger's system configuration? Thus far neither the above test nor any of the configure scripts mentioned are reproducing the panic over here. As a first hunch I tried switching to a cyrillic locale but that made no difference. hrev45350, gcc4, 8GB of RAM and 8 CPU cores over here for reference.

Strange, it is reproducible both in Virtual Box and with real HW on my home system. May be our /Sources partitions that were created years ago affect on this. I'll check more widely than.

[siarzhuk]

I have checked bison.c test on following systems:

hrev42604 GCC4/Hybrid (in VirtualBox)
hrevalpha4-44594
hrev45141 x86_64
hrev43037 GCC4/Hybrid
hrev45223 GCC4/Hybrid
hrev44869 GCC4/Hybrid

test on all systems fails with the same error. :-|

[anevilyak]

Always with the same set of partitions? Or does e.g. a completely clean virtualbox image with no other partitions mounted exhibit the same issue?

[siarzhuk]

Replying to anevilyak:

Always with the same set of partitions? Or does e.g. a completely clean virtualbox image with no other partitions mounted exhibit the same issue?

By the way the VirtualBox case above (#1) is such "completely clean". 2,3,4 - different partitions of the same PC. 5,6 - different partitions of the other PC. BTW diger.png acquired on Virtual Box at my PC on the work. I have tested all cases by copying bison.c to home directory issuing "gcc bison.c" and running resulting a.out file.

[anevilyak]

Replying to siarzhuk:

By the way the VirtualBox case above (#1) is such "completely clean". 2,3,4 - different partitions of the same PC. 5,6 - different partitions of the other PC. BTW diger.png acquired on Virtual Box at my PC on the work. I have tested all cases by copying bison.c to home directory issuing "gcc bison.c" and running resulting a.out file.

Tried exactly those steps, still no luck. Could you by any chance try enabling VFS tracing (​http://cgit.haiku-os.org/haiku/tree/src/system/kernel/fs/vfs.cpp#n66 ), and then paste the resulting serial output from vbox here?

[siarzhuk]

cutout of crash log

[siarzhuk]

Replying to anevilyak:

Could you by any chance try enabling VFS tracing (​http://cgit.haiku-os.org/haiku/tree/src/system/kernel/fs/vfs.cpp#n66 ), and then paste the resulting serial output from vbox here?

It was a bit tricky: First I have to disable syslog because it never ends tracing into system log about it's writing into system log, I suspect. Than I have to unsuccessfully wait about 3 hours until it finish loading app_server and other whistles. Than I just hardcoded "launch /bin/consoled" into boot script and get the possibility to run a.out and get KDL. :-) I hope it helps.

[tidux]

I was able to reproduce this on both hrev45480 and hrev45526 when attempting to configure groff 1.22.2, on a physical machine and a virtual machine. Here's a screenshot of the VM crashing.