Different behaviours of GEOSIntersection (C API) according to the arguments order

[plx]

(sorry for my English - I am French)

Two simple geometries (LINESTRING). The first vertex of geometry 1 equals the last vertex of geometry 2 (see attached files edge1.hexwkb and edge2.hexwkb in hex-wkb format).

The call "GEOSIntersection(geometry1,geometry2)" returns a POINT geometry, with the common vertex as result.

The call "GEOSIntersection(geometry2,geometry1)" implies a segmentation fault (see "Print Screen" file with the messages of my debugger - copy/paste of the messages doesn't work)

Even if I use the C API of the library, I don't think it is linked so I put this ticket in the "Core" component