Opened 15 years ago
Closed 15 years ago
#466 closed defect (fixed)
test_rect_tree_contains_point segfaults
Reported by: | strk | Owned by: | pramsey |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 1.5.2 |
Component: | postgis | Version: | 1.5.X |
Keywords: | Cc: |
Description ¶
Running test 'test_rect_tree_contains_point' in suite 'PostGIS Measures Suite'.
Program received signal SIGSEGV, Segmentation fault. 0x000000000040a217 in test_rect_tree_contains_point () at cu_measures.c:130 130 tree = rect_tree_new(poly→rings[0]); (gdb) bt #0 0x000000000040a217 in test_rect_tree_contains_point () at cu_measures.c:130 #1 0x00007f0a5821945a in ?? () from /usr/lib/libcunit.so.1 #2 0x00007f0a58219877 in CU_run_test () from /usr/lib/libcunit.so.1 #3 0x000000000040e2e4 in main (argc=2, argv≤value optimized out>)
at cu_tester.c:118
At revision 5443. Did ./autogen.sh; ./configure && make clean && make && make check
Change History (7)
comment:1 by , 15 years ago
follow-up: 3 comment:2 by , 15 years ago
There's not much code there… it's like the actual from EWKT process is failing? But that implies parser stuff is failing, which implies…?
comment:3 by , 15 years ago
Replying to pramsey:
There's not much code there… it's like the actual from EWKT process is failing? But that implies parser stuff is failing, which implies…?
No idea
Maybe that 'make clean' failed to clean some of the parser stuff ?
Versions here:
bison (GNU Bison) 2.3 flex 2.5.35
comment:5 by , 15 years ago
I couldn't replicate it by regenerating the parser files either. And in any event the generated files haven't been touched since November of last year.
comment:6 by , 15 years ago
My segfault is also a moving target. This time it happened here:
Test: test_ptarray_point_in_ring … make[1]: * [check] Segmentation fault
comment:7 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Alright, as of r5445 'make clean' does what it's supposed to do, and next build&check after make clean now succeeds with no failures nor segfaults.
I'm afraid dependencies are still a big mess, but at least you can clean now.
Valgrind log: