[GRASS-dev] [GRASS GIS] #3006: Large attribute table causes buffer overflow in v.db.select
GRASS GIS
trac at osgeo.org
Wed Apr 27 13:51:56 PDT 2016
#3006: Large attribute table causes buffer overflow in v.db.select
--------------------------+-------------------------
Reporter: marisn | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.1.0
Component: wxGUI | Version: svn-trunk
Resolution: | Keywords: v.db.select
CPU: Unspecified | Platform: Linux
--------------------------+-------------------------
Comment (by annakrat):
Replying to [comment:2 marisn]:
> Replying to [comment:1 annakrat]:
> > Aren't these 2 separate issues? First is v.db.select crashing and
second is opening large tables in attribute table manager.
> I haven't been reading the code, still I believe the overflow is caused
by behaviour of wxGUI as it happened when I was trying to view attribute
table of vector map. The question is if we should fix v.db.selec as many
parts of GRASS would fail if abused (just grep for fixed buffer sizes in C
files to get an idea).
The backtrace comes from v.db.select, so we should start there. Loading
data in attribute manager is separate issue. Run v.db.select from command
line, you should get the backtrace. But to fix it we need reproducible
example, so if you can't reproduce it on North Carolina, your data is
needed or at least a way to generate the data which lead to the crash.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3006#comment:3>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list