Opened 15 years ago

Closed 15 years ago

#380 closed defect (fixed) segfault in dig_alloc_points

Reported by: msieczka Owned by: grass-dev@…
Priority: critical Milestone: 6.4.0
Component: Vector Version: svn-develbranch6
Keywords: Cc:
CPU: x86-64 Platform: Linux


GRASS 6.4 SVN r34374, Debian testing amd64.

$ gdb

(gdb) run ainput=gshhs_f_land atype=line alayer=1 binput=region btype=line blayer=1 output=sel operator=overlap --o

Starting program: /usr/local/grass-6.4.svn/bin/ ainput=gshhs_f_land@PERMANENT atype=line alayer=1 binput=region@PERMANENT btype=line blayer=1 output=sel operator=overlap --o
[Thread debugging using libthread_db enabled]
warning: Lowest section in /usr/lib/ is .hash at 0000000000000120
[New Thread 0x7ff2df7ed710 (LWP 16527)]
WARNING: Vector map <sel> already exists and will be overwritten
Processing vector features...

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ff2df7ed710 (LWP 16527)]
0x00007ff2de5f488a in dig_alloc_points (points=0x0, num=1)
    at struct_alloc.c:237
237	    alloced = points->alloc_points;
(gdb) bt
#0  0x00007ff2de5f488a in dig_alloc_points (points=0x0, num=1)
    at struct_alloc.c:237
#1  0x00007ff2df4e9a8b in Vect_copy_xyz_to_pnts (Points=0x0, x=0x7fffe7923320, 
    y=0x7fffe7923318, z=0x7fffe7923310, n=1) at line.c:118
#2  0x00007ff2df4e854d in find_cross (id=2, arg=0x7fffe7923444)
    at intersect.c:1095
#3  0x00007ff2de3dc962 in RTreeSearch (N=0x39bbbd0, R=0x7fffe7923400, 
    shcb=0x7ff2df4e82e5 <find_cross>, cbarg=0x7fffe7923444) at index.c:65
#4  0x00007ff2df4e8e42 in Vect_line_check_intersection (APoints=0x39b6250, 
    BPoints=0x39b7820, with_z=0) at intersect.c:1273
#5  0x0000000000402a44 in main (argc=10, argv=0x7fffe7924988) at main.c:270

Change History (2)

comment:1 by martinl, 15 years ago

Already fixed in 6.4 (r34468) and 7.0 (r34469). Martin

in reply to:  1 comment:2 by msieczka, 15 years ago

Resolution: fixed
Status: newclosed

Replying to martinl:

Already fixed in 6.4 (r34468) and 7.0 (r34469). Martin

Indeed. Thanks!

Note: See TracTickets for help on using tickets.