[GRASS-dev] FTBFS: segmentation fault in lib/vector/diglib/test.c

GRASS GIS GRASS GIS developer
1

Hi,

by chance I found this report in the Fedora 19 bugtracker:

FTBFS: segmentation fault in lib/vector/diglib/test.c
https://bugzilla.redhat.com/show_bug.cgi?id=961838

-> Segmentation fault, looks like integer overflow.
Does anybody see the issue?

Markus

2

On Thu, May 23, 2013 at 10:53 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

by chance I found this report in the Fedora 19 bugtracker:

FTBFS: segmentation fault in lib/vector/diglib/test.c
https://bugzilla.redhat.com/show_bug.cgi?id=961838

-> Segmentation fault, looks like integer overflow.
Does anybody see the issue?

Fixed August 2011 in trunk r47992.

This affects only big endian systems.

Markus M

3

On Fri, May 24, 2013 at 8:24 AM, Markus Metz
<markus.metz.giswork@gmail.com> wrote:

On Thu, May 23, 2013 at 10:53 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

by chance I found this report in the Fedora 19 bugtracker:

FTBFS: segmentation fault in lib/vector/diglib/test.c
https://bugzilla.redhat.com/show_bug.cgi?id=961838

-> Segmentation fault, looks like integer overflow.
Does anybody see the issue?

Fixed August 2011 in trunk r47992.

Can I backport it then?

This affects only big endian systems.

ok.

Markus

4

On Fri, May 24, 2013 at 9:42 AM, Markus Neteler <neteler@osgeo.org> wrote:

On Fri, May 24, 2013 at 8:24 AM, Markus Metz
<markus.metz.giswork@gmail.com> wrote:

On Thu, May 23, 2013 at 10:53 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi,

by chance I found this report in the Fedora 19 bugtracker:

FTBFS: segmentation fault in lib/vector/diglib/test.c
https://bugzilla.redhat.com/show_bug.cgi?id=961838

-> Segmentation fault, looks like integer overflow.
Does anybody see the issue?

Fixed August 2011 in trunk r47992.

Can I backport it then?

In theory yes, but only the changes introduced with r47992, not the
current version of lib/vector/diglib/portable.c in trunk.

The diglib test might then fail.

This affects only big endian systems.

I was wrong, the portability test simulates a little endian and a big
endian system and can thus cause a segfault on any system.

Markus M