"g.mlist rast pat=hpf* mapset=pre-processing_post"
gives a "Segmentation fault". Is the dash an unwanted character in naming
Mapsets? I don't see a segfault with "normal" Mapset names.
Nikos
"g.mlist rast pat=hpf* mapset=pre-processing_post"
gives a "Segmentation fault". Is the dash an unwanted character in naming
Mapsets? I don't see a segfault with "normal" Mapset names.
Nikos
As dash in some contexts (hypothetically) can be interpreted as a
minus sign (pre minus processing), I would say it's a bug that you
were able to create a mapset with such name.
Just open a ticket in trac for the tool you used to create mapset.
Maris.
2013/12/8 Nikos Alexandris <nik@nikosalexandris.net>:
"g.mlist rast pat=hpf* mapset=pre-processing_post"
gives a "Segmentation fault". Is the dash an unwanted character in naming
Mapsets? I don't see a segfault with "normal" Mapset names.Nikos
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Nikos Alexandris wrote:
"g.mlist rast pat=hpf* mapset=pre-processing_post"
gives a "Segmentation fault". Is the dash an unwanted character in naming
Mapsets? I don't see a segfault with "normal" Mapset names.
A dash is supposed to be valid in names of maps, mapsets, locations,
etc.
This is one of the main reasons why r.mapcalc supports quoting of map
names.
FWIW, I can't reproduce the issue in 7.0 with a simple test case.
--
Glynn Clements <glynn@gclements.plus.com>