Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-11 Thread Yavor Doganov
On Wed, 09 Jan 2019 22:42:43 +0200, Andreas Tille wrote: > The values of the structure are set in line 350[3] and are OK there. What looks suspicious to me is that an unsigned long long value is assigned to struct members of type size_t. In the previous upstream release that worked, the return

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-10 Thread Andreas Tille
Hi Sune, On Thu, Jan 10, 2019 at 06:27:47PM +, Sune Vuorela wrote: > ... > I looked briefly at the code, but I didn't feel like actually trying to > understand what's going on. Thanks a lot for this detailed analysis. I'll forward it to bug #907624 and the upstream issue[1]. I admit I also

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-10 Thread Sune Vuorela
On 2019-01-09, Andrey Rahmatullin wrote: > As usual: reading the code, debugging, printfs. Address sanitizer and/or > valgrind may or may not help too. I just tried throwing some tools at it. Apparantly you need a three step thing to get to it. address-sanitizer. First issue. The command to

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-09 Thread Andrey Rahmatullin
On Wed, Jan 09, 2019 at 10:49:48PM +0100, Andreas Tille wrote: > > > to find the exact code line[2] where the SIGSEGV is thrown. It turns out > > > that the elements of a structure are not accessible: > > > > > >(gdb) print entry->offset > > >Cannot access memory at address 0x7 > > It's

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-09 Thread Andreas Tille
Hi, On Thu, Jan 10, 2019 at 02:14:14AM +0500, Andrey Rahmatullin wrote: > On Wed, Jan 09, 2019 at 09:42:43PM +0100, Andreas Tille wrote: > > to find the exact code line[2] where the SIGSEGV is thrown. It turns out > > that the elements of a structure are not accessible: > > > >(gdb) print

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-09 Thread Ole Streicher
Hi Andreas, one thing I usually do in such cases is to rebuild the package adding "-fsanitize=address -O0" flags (optimization just to understand better what happens in the source). This switches the address sanitizer on . This can test

Re: Help for SIGSEGV in test suite needed when built with gcc 8.2 what works nicely with gcc 6.3

2019-01-09 Thread Andrey Rahmatullin
On Wed, Jan 09, 2019 at 09:42:43PM +0100, Andreas Tille wrote: > to find the exact code line[2] where the SIGSEGV is thrown. It turns out > that the elements of a structure are not accessible: > >(gdb) print entry->offset >Cannot access memory at address 0x7 It's because entry is 0x7. >