[GRASS-dev] g.copy rast=

hi list,

with the recent cvs version of grass63 g.copy for raster maps doesn't work any
more. i just get a meaningless 'memory access error' (speicherzugriffsfehler).
runinng configure, make, make install gives no error messages.

g.gisenv set="DEBUG=5"

g.copy rast=raster1,raster2
D3/5: Copy rast
Copy <raster1@hohenems_site> to current mapset as <raster2>
Speicherzugriffsfehler

r.info raster2
D2/5: G__home home = /home/rusch
WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
WARNUNG: Kategorie Unterstützung für [raster2] im Mapset [hohenems_site]
         missing
WARNUNG: Kann die History-Informationen der Karte [raster2] in Mapset
         [hohenems_site] nicht finden.
WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht lesen.
FEHLER: Kann die Wertespanne nicht lesen.

the problem appears on FC4,FC5 and FC6 aswell with following configuration:

FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
--with-gdal=/usr/local/bin/gdal-config --with-tcltk-includes=/usr/local/include
--with-postgres-includes=/usr/local/pgsql/include
--with-postgres-libs=/usr/local/pgsql/lib
--with-freetype-includes=/usr/include/freetype2 --with-freetype-libs=/usr/lib
--enable-largefile --with-odbc --with-motif --with-freetype=yes --with-cxx
--with-glw --with-nls --with-blas --with-lapack
--with-lapack-libs=/usr/local/lib --with-ffmpeg
--with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
--with-proj-share=/usr/local/share/proj/ --enable-64bit --with-python

i don't know which libs/pkg are used by g.copy; but i tried different versions
of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn; tcl/tk8.5a5/tcl/tk8.4.14) but it
seems to me that it's not dependent on a certain version of a package.

thanks alot!
martin

Hi,

it is strange, on my machine g.copy works. What does gdb say?

Martin

2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:

hi list,

with the recent cvs version of grass63 g.copy for raster maps doesn't work any
more. i just get a meaningless 'memory access error' (speicherzugriffsfehler).
runinng configure, make, make install gives no error messages.

g.gisenv set="DEBUG=5"

g.copy rast=raster1,raster2
D3/5: Copy rast
Copy <raster1@hohenems_site> to current mapset as <raster2>
Speicherzugriffsfehler

r.info raster2
D2/5: G__home home = /home/rusch
WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
WARNUNG: Kategorie Unterstützung für [raster2] im Mapset [hohenems_site]
         missing
WARNUNG: Kann die History-Informationen der Karte [raster2] in Mapset
         [hohenems_site] nicht finden.
WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht lesen.
FEHLER: Kann die Wertespanne nicht lesen.

the problem appears on FC4,FC5 and FC6 aswell with following configuration:

FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
--with-gdal=/usr/local/bin/gdal-config --with-tcltk-includes=/usr/local/include
--with-postgres-includes=/usr/local/pgsql/include
--with-postgres-libs=/usr/local/pgsql/lib
--with-freetype-includes=/usr/include/freetype2 --with-freetype-libs=/usr/lib
--enable-largefile --with-odbc --with-motif --with-freetype=yes --with-cxx
--with-glw --with-nls --with-blas --with-lapack
--with-lapack-libs=/usr/local/lib --with-ffmpeg
--with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
--with-proj-share=/usr/local/share/proj/ --enable-64bit --with-python

i don't know which libs/pkg are used by g.copy; but i tried different versions
of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn; tcl/tk8.5a5/tcl/tk8.4.14) but it
seems to me that it's not dependent on a certain version of a package.

thanks alot!
martin

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy "rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870 "hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

Hi,

it is strange, on my machine g.copy works. What does gdb say?

Martin

2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
> hi list,
>
> with the recent cvs version of grass63 g.copy for raster maps doesn't work
any
> more. i just get a meaningless 'memory access error'
(speicherzugriffsfehler).
> runinng configure, make, make install gives no error messages.
>
> g.gisenv set="DEBUG=5"
>
> g.copy rast=raster1,raster2
> D3/5: Copy rast
> Copy <raster1@hohenems_site> to current mapset as <raster2>
> Speicherzugriffsfehler
>
> r.info raster2
> D2/5: G__home home = /home/rusch
> WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
> WARNUNG: Kategorie Unterstützung für [raster2] im Mapset [hohenems_site]
> missing
> WARNUNG: Kann die History-Informationen der Karte [raster2] in Mapset
> [hohenems_site] nicht finden.
> WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht lesen.
> FEHLER: Kann die Wertespanne nicht lesen.
>
>
>
> the problem appears on FC4,FC5 and FC6 aswell with following configuration:
>
> FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
> --with-gdal=/usr/local/bin/gdal-config
--with-tcltk-includes=/usr/local/include
> --with-postgres-includes=/usr/local/pgsql/include
> --with-postgres-libs=/usr/local/pgsql/lib
> --with-freetype-includes=/usr/include/freetype2
--with-freetype-libs=/usr/lib
> --enable-largefile --with-odbc --with-motif --with-freetype=yes --with-cxx
> --with-glw --with-nls --with-blas --with-lapack
> --with-lapack-libs=/usr/local/lib --with-ffmpeg
> --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
> --with-proj-share=/usr/local/share/proj/ --enable-64bit --with-python
>
> i don't know which libs/pkg are used by g.copy; but i tried different
versions
> of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn; tcl/tk8.5a5/tcl/tk8.4.14)
but it
> seems to me that it's not dependent on a certain version of a package.
>
> thanks alot!
> martin
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

hi,

cause i'm not familiar with grass c programming, i'm not sure what information
you need for error detection. so i followed the grass debugging manual on the
WIKI.

thanks,
martin

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run rast=rott_one,test1
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy rast=rott_one,test1
[Thread debugging using libthread_db enabled]
[New Thread -1208621360 (LWP 13741)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208621360 (LWP 13741)]
do_copy (n=0, old=0x8adc838 "rott_one", mapset=0x8adc870 "hohenems_site",
new=0x8adc848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb) bt full
#0 do_copy (n=0, old=0x8adc838 "rott_one", mapset=0x8adc870 "hohenems_site",
new=0x8adc848 "test1") at do_copy.c:40
        i = 0
        ret = <value optimized out>
        path =
"/data/grassdb/utm/hohenems_site/cell/rott_one\000-&#65533;M\\&#65533;dc\000\000&#65533;&#1079;\000\000\000R&#65533;\023Ndc\000\000&#65533;&#1079;\034&#65533;8&#65533;\024&#65533;&#65533;\031N\224&#1663;\224&#1663;,&#65533;=l\031N\224&#1663;\000\000\000\000\000\000\000\000}\004\bx&#1663;\235&#65533;027N$&#1663;\000\000\000\000\224&#1663;\001\000\000\000&#65533;wM&#65533;wM\004\033&#65533;234&#65533;&#65533;&#1663;-&#65533;M,&#65533;$wM\027\000\000\000\034&#65533;000\n&#288;"...
        path2 =
"/data/grassdb/utm/hohenems_site/cell/test1\000\000\000\000\005\000\000\000\b&#65533;&#65533;\003\000\000\000H&#65533;&#65533;&N&#65533;&NH&#65533;D&#65533;X&#65533;\002",
'\0' <repeats 11 times>,
"\200\b\006\000\000\000X&#65533;&#65533;031\033N\b8//\000&#65533;
&#65533;&#65533;\230\b\210)&#1655;\000\000\000\000\000\000\000\0000\b\000\000\000\000&#65533;&N\b0\b\025N&#65533;&#1663;rq\032N\b\210&#65533;&#65533;\b\000\000\000"...
        result = 0
#1 0x08049453 in main (argc=2, argv=0xbfd9fbd4) at copy.c:80
        n = <value optimized out>
        mapset = 0x8adc870 "hohenems_site"
        module = (struct GModule *) 0xcb3710
        parm = (struct Option **) 0x8adbb68
        p = <value optimized out>
        to = 0x8adc848 "test1"
        buf1 =
"&#65533;&#1663;\000\000\000\000\000\000\000\000\001\000\000\000F\b\000\000&#65533;033&#65533;&#65533;\212\004\bd\b\024N\203\004\b\001\000\000\000&#65533;wM\200wM<&#1663;X&#1663;P&#65533;M\203\004\b<&#1663;$wM\027\000\000\000&#65533;033&#65533;001\000\000\000\000\000\000\000\001\000\000\000\001\000\000\000\001\000\000\000\000\000\000\000\235A&\000H&#1663;\004\023NR&#65533;&#65533;\000&#65533;wM&#65533;&#65533;&#65533;000\200&#1663;&#65533;wMo\212\004\b\001\000\000\000\001\000\000\000\001\000\000\000.N=&#65533;000\000\000\000\000\200&#65533;000\220<9\000\025NX$\001\b&#65533;\001&#65533;&N"...
        location_path = 0x8adc858 "/data/grassdb/utm"
        result = 0
(gdb) l
35 G_warning ("Cannot copy <%s> to current mapset as <%s>",
36 G_fully_qualified_name(old, mapset), new );
37 result = 1;
38 }
39 } else {
40 for (i = 0; i < list[n].nelem; i++)
41 {
42 G__make_mapset_element (list[n].element[i]);
43 G__file_name (path, list[n].element[i], old, mapset);
44 if (access (path, 0) != 0)
(gdb) frame 2
#0 0x00000000 in ?? ()
(gdb) l
45 {
46 G_remove (list[n].element[i], new);
47 if (G_verbose() == G_verbose_max())
48 G_message (_("%s: missing"), list[n].desc[i]);
49
50 continue;
51 }
52 G__file_name (path2, list[n].element[i], new, G_mapset());
53 if ( recursive_copy(path, path2) == 1 )
54 {

Zitat von Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy "rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870 "hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

> Hi,
>
> it is strange, on my machine g.copy works. What does gdb say?
>
> Martin
>
> 2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
> > hi list,
> >
> > with the recent cvs version of grass63 g.copy for raster maps doesn't
work
> any
> > more. i just get a meaningless 'memory access error'
> (speicherzugriffsfehler).
> > runinng configure, make, make install gives no error messages.
> >
> > g.gisenv set="DEBUG=5"
> >
> > g.copy rast=raster1,raster2
> > D3/5: Copy rast
> > Copy <raster1@hohenems_site> to current mapset as <raster2>
> > Speicherzugriffsfehler
> >
> > r.info raster2
> > D2/5: G__home home = /home/rusch
> > WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
> > WARNUNG: Kategorie Unterstützung für [raster2] im Mapset [hohenems_site]
> > missing
> > WARNUNG: Kann die History-Informationen der Karte [raster2] in Mapset
> > [hohenems_site] nicht finden.
> > WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht lesen.
> > FEHLER: Kann die Wertespanne nicht lesen.
> >
> >
> >
> > the problem appears on FC4,FC5 and FC6 aswell with following
configuration:
> >
> > FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
> > --with-gdal=/usr/local/bin/gdal-config
> --with-tcltk-includes=/usr/local/include
> > --with-postgres-includes=/usr/local/pgsql/include
> > --with-postgres-libs=/usr/local/pgsql/lib
> > --with-freetype-includes=/usr/include/freetype2
> --with-freetype-libs=/usr/lib
> > --enable-largefile --with-odbc --with-motif --with-freetype=yes
--with-cxx
> > --with-glw --with-nls --with-blas --with-lapack
> > --with-lapack-libs=/usr/local/lib --with-ffmpeg
> > --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
> > --with-proj-share=/usr/local/share/proj/ --enable-64bit --with-python
> >
> > i don't know which libs/pkg are used by g.copy; but i tried different
> versions
> > of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn; tcl/tk8.5a5/tcl/tk8.4.14)
> but it
> > seems to me that it's not dependent on a certain version of a package.
> >
> > thanks alot!
> > martin
> >
> >
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev@grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grass-dev
> >
>
>
> --
> Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *
>

Martin,

I can confirm a segfault on using g.copy, with today's CVS on Ubuntu 6.06.

g.copy exits with a segfault, but the maps seems to get copied to the destination mapset as requested anyway. Only the command line run reaches a segfault, not the GUI version. Or maybe the error just isn't visible from the GUI.

Output from gdb:

$ gdb `which g.copy`
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
[Thread debugging using libthread_db enabled]
[New Thread -1224742304 (LWP 7624)]
Copy <Mispec_Apr2000.grd@UNB_Original_r4s> to current mapset as <TEST_2>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224742304 (LWP 7624)]
0xb7eda963 in G_strcasecmp (x=0x804d800 "cell", y=0x532d87 <Address 0x532d87 out of bounds>) at strings.c:146
146 while (*x && *y)
(gdb)

Devs, any other info needed to diagnose this error?

~ Eric.

-----Original Message-----
From: grass-dev-bounces@grass.itc.it
To: Martin Landa
Cc: grass-dev
Sent: 2/19/2007 8:51 AM
Subject: Re: [GRASS-dev] g.copy rast=

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
"rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870
"hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

Hi,

it is strange, on my machine g.copy works. What does gdb say?

Martin

2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
> hi list,
>
> with the recent cvs version of grass63 g.copy for raster maps

doesn't work

any
> more. i just get a meaningless 'memory access error'
(speicherzugriffsfehler).
> runinng configure, make, make install gives no error messages.
>
> g.gisenv set="DEBUG=5"
>
> g.copy rast=raster1,raster2
> D3/5: Copy rast
> Copy <raster1@hohenems_site> to current mapset as <raster2>
> Speicherzugriffsfehler
>
> r.info raster2
> D2/5: G__home home = /home/rusch
> WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
> WARNUNG: Kategorie Unterstützung für [raster2] im Mapset

[hohenems_site]

> missing
> WARNUNG: Kann die History-Informationen der Karte [raster2] in

Mapset

> [hohenems_site] nicht finden.
> WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht

lesen.

> FEHLER: Kann die Wertespanne nicht lesen.
>
>
>
> the problem appears on FC4,FC5 and FC6 aswell with following

configuration:

>
> FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
> --with-gdal=/usr/local/bin/gdal-config
--with-tcltk-includes=/usr/local/include
> --with-postgres-includes=/usr/local/pgsql/include
> --with-postgres-libs=/usr/local/pgsql/lib
> --with-freetype-includes=/usr/include/freetype2
--with-freetype-libs=/usr/lib
> --enable-largefile --with-odbc --with-motif --with-freetype=yes

--with-cxx

> --with-glw --with-nls --with-blas --with-lapack
> --with-lapack-libs=/usr/local/lib --with-ffmpeg
> --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
> --with-proj-share=/usr/local/share/proj/ --enable-64bit

--with-python

>
> i don't know which libs/pkg are used by g.copy; but i tried

different

versions
> of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn;

tcl/tk8.5a5/tcl/tk8.4.14)

but it
> seems to me that it's not dependent on a certain version of a

package.

>
> thanks alot!
> martin
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa

*

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

Hi,

did you use

make distclean

before compiling GRASS? Not sure, maybe it helps.

Martin

2007/2/19, Patton, Eric <epatton@nrcan.gc.ca>:

Martin,

I can confirm a segfault on using g.copy, with today's CVS on Ubuntu 6.06.

g.copy exits with a segfault, but the maps seems to get copied to the destination mapset as requested anyway. Only the command line run reaches a segfault, not the GUI version. Or maybe the error just isn't visible from the GUI.

Output from gdb:

$ gdb `which g.copy`
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
[Thread debugging using libthread_db enabled]
[New Thread -1224742304 (LWP 7624)]
Copy <Mispec_Apr2000.grd@UNB_Original_r4s> to current mapset as <TEST_2>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224742304 (LWP 7624)]
0xb7eda963 in G_strcasecmp (x=0x804d800 "cell", y=0x532d87 <Address 0x532d87 out of bounds>) at strings.c:146
146 while (*x && *y)
(gdb)

Devs, any other info needed to diagnose this error?

~ Eric.

-----Original Message-----
From: grass-dev-bounces@grass.itc.it
To: Martin Landa
Cc: grass-dev
Sent: 2/19/2007 8:51 AM
Subject: Re: [GRASS-dev] g.copy rast=

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
"rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870
"hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

> Hi,
>
> it is strange, on my machine g.copy works. What does gdb say?
>
> Martin
>
> 2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
> > hi list,
> >
> > with the recent cvs version of grass63 g.copy for raster maps
doesn't work
> any
> > more. i just get a meaningless 'memory access error'
> (speicherzugriffsfehler).
> > runinng configure, make, make install gives no error messages.
> >
> > g.gisenv set="DEBUG=5"
> >
> > g.copy rast=raster1,raster2
> > D3/5: Copy rast
> > Copy <raster1@hohenems_site> to current mapset as <raster2>
> > Speicherzugriffsfehler
> >
> > r.info raster2
> > D2/5: G__home home = /home/rusch
> > WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
> > WARNUNG: Kategorie Unterstützung für [raster2] im Mapset
[hohenems_site]
> > missing
> > WARNUNG: Kann die History-Informationen der Karte [raster2] in
Mapset
> > [hohenems_site] nicht finden.
> > WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht
lesen.
> > FEHLER: Kann die Wertespanne nicht lesen.
> >
> > the problem appears on FC4,FC5 and FC6 aswell with following
configuration:
> >
> > FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
> > --with-gdal=/usr/local/bin/gdal-config
> --with-tcltk-includes=/usr/local/include
> > --with-postgres-includes=/usr/local/pgsql/include
> > --with-postgres-libs=/usr/local/pgsql/lib
> > --with-freetype-includes=/usr/include/freetype2
> --with-freetype-libs=/usr/lib
> > --enable-largefile --with-odbc --with-motif --with-freetype=yes
--with-cxx
> > --with-glw --with-nls --with-blas --with-lapack
> > --with-lapack-libs=/usr/local/lib --with-ffmpeg
> > --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
> > --with-proj-share=/usr/local/share/proj/ --enable-64bit
--with-python
> >
> > i don't know which libs/pkg are used by g.copy; but i tried
different
> versions
> > of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn;
tcl/tk8.5a5/tcl/tk8.4.14)
> but it
> > seems to me that it's not dependent on a certain version of a
package.
> >
> > thanks alot!
> > martin
> >
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev@grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grass-dev
> >
>
> --
> Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa
*
>

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

Martin,

Yes, I ran make distclean before compiling.

~ Eric.

-----Original Message-----
From: Martin Landa
To: Patton, Eric
Cc: Martin Rutzinger; grass-dev
Sent: 2/19/2007 10:40 AM
Subject: Re: [GRASS-dev] g.copy rast=

Hi,

did you use

make distclean

before compiling GRASS? Not sure, maybe it helps.

Martin

2007/2/19, Patton, Eric <epatton@nrcan.gc.ca>:

Martin,

I can confirm a segfault on using g.copy, with today's CVS on Ubuntu

6.06.

g.copy exits with a segfault, but the maps seems to get copied to the

destination mapset as requested anyway. Only the command line run
reaches a segfault, not the GUI version. Or maybe the error just isn't
visible from the GUI.

Output from gdb:

$ gdb `which g.copy`
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and

you are

welcome to change it and/or distribute copies of it under certain

conditions.

Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for

details.

This GDB was configured as "i486-linux-gnu"...Using host libthread_db

library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy

rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2

[Thread debugging using libthread_db enabled]
[New Thread -1224742304 (LWP 7624)]
Copy <Mispec_Apr2000.grd@UNB_Original_r4s> to current mapset as

<TEST_2>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224742304 (LWP 7624)]
0xb7eda963 in G_strcasecmp (x=0x804d800 "cell", y=0x532d87 <Address

0x532d87 out of bounds>) at strings.c:146

146 while (*x && *y)
(gdb)

Devs, any other info needed to diagnose this error?

~ Eric.

-----Original Message-----
From: grass-dev-bounces@grass.itc.it
To: Martin Landa
Cc: grass-dev
Sent: 2/19/2007 8:51 AM
Subject: Re: [GRASS-dev] g.copy rast=

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
"rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870
"hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

> Hi,
>
> it is strange, on my machine g.copy works. What does gdb say?
>
> Martin
>
> 2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
> > hi list,
> >
> > with the recent cvs version of grass63 g.copy for raster maps
doesn't work
> any
> > more. i just get a meaningless 'memory access error'
> (speicherzugriffsfehler).
> > runinng configure, make, make install gives no error messages.
> >
> > g.gisenv set="DEBUG=5"
> >
> > g.copy rast=raster1,raster2
> > D3/5: Copy rast
> > Copy <raster1@hohenems_site> to current mapset as <raster2>
> > Speicherzugriffsfehler
> >
> > r.info raster2
> > D2/5: G__home home = /home/rusch
> > WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
> > WARNUNG: Kategorie Unterstützung für [raster2] im Mapset
[hohenems_site]
> > missing
> > WARNUNG: Kann die History-Informationen der Karte [raster2] in
Mapset
> > [hohenems_site] nicht finden.
> > WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht
lesen.
> > FEHLER: Kann die Wertespanne nicht lesen.
> >
> >
> >
> > the problem appears on FC4,FC5 and FC6 aswell with following
configuration:
> >
> > FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
> > --with-gdal=/usr/local/bin/gdal-config
> --with-tcltk-includes=/usr/local/include
> > --with-postgres-includes=/usr/local/pgsql/include
> > --with-postgres-libs=/usr/local/pgsql/lib
> > --with-freetype-includes=/usr/include/freetype2
> --with-freetype-libs=/usr/lib
> > --enable-largefile --with-odbc --with-motif --with-freetype=yes
--with-cxx
> > --with-glw --with-nls --with-blas --with-lapack
> > --with-lapack-libs=/usr/local/lib --with-ffmpeg
> > --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
> > --with-proj-share=/usr/local/share/proj/ --enable-64bit
--with-python
> >
> > i don't know which libs/pkg are used by g.copy; but i tried
different
> versions
> > of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn;
tcl/tk8.5a5/tcl/tk8.4.14)
> but it
> > seems to me that it's not dependent on a certain version of a
package.
> >
> > thanks alot!
> > martin
> >
> >
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev@grass.itc.it
> > http://grass.itc.it/mailman/listinfo/grass-dev
> >
>
>
> --
> Martin Landa <landa.martin@gmail.com> *

http://gama.fsv.cvut.cz/~landa

*
>

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

On 19/02/07 16:45, Patton, Eric wrote:

Martin,

Yes, I ran make distclean before compiling.

Just to let you know, that I cannot reproduce this with a freshly compiled CVS tree on Debian...

Moritz

Hi,
i can not reproduce this error with the today's grass-CVS build on Debian etch. The grass test suite produces no errors:

GRASS 6.3.cvs > ./RunGRASSTestSuite.sh -g

Start testing general (g.*) modules

g.copy test: success success success success finished
g.findfile test: success finished
g.filename test: success finished
g.remove test: success success success success success success success success finished
g.rename test: success success success success success success success success finished
g.proj output test: success success success success success success success finished
g.tempfile test: success finished
g.gisenv test: success success finished
g.list test: success success success success success success success success success success success finished
g.region output test: success success success success success success success finished
g.version test: success success success finished

Finished testing general (g.*) modules

Soeren

Patton, Eric schrieb:

Martin,

I can confirm a segfault on using g.copy, with today's CVS on Ubuntu 6.06.

g.copy exits with a segfault, but the maps seems to get copied to the destination mapset as requested anyway. Only the command line run reaches a segfault, not the GUI version. Or maybe the error just isn't visible from the GUI.

Output from gdb:

$ gdb `which g.copy`
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
[Thread debugging using libthread_db enabled]
[New Thread -1224742304 (LWP 7624)]
Copy <Mispec_Apr2000.grd@UNB_Original_r4s> to current mapset as <TEST_2>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224742304 (LWP 7624)]
0xb7eda963 in G_strcasecmp (x=0x804d800 "cell", y=0x532d87 <Address 0x532d87 out of bounds>) at strings.c:146
146 while (*x && *y)
(gdb)

Devs, any other info needed to diagnose this error?

~ Eric.

-----Original Message-----
From: grass-dev-bounces@grass.itc.it
To: Martin Landa
Cc: grass-dev
Sent: 2/19/2007 8:51 AM
Subject: Re: [GRASS-dev] g.copy rast=

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
"rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870
"hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

Zitat von Martin Landa <landa.martin@gmail.com>:

Hi,

it is strange, on my machine g.copy works. What does gdb say?

Martin

2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:

hi list,

with the recent cvs version of grass63 g.copy for raster maps

doesn't work

any

more. i just get a meaningless 'memory access error'

(speicherzugriffsfehler).

runinng configure, make, make install gives no error messages.

g.gisenv set="DEBUG=5"

g.copy rast=raster1,raster2
D3/5: Copy rast
Copy <raster1@hohenems_site> to current mapset as <raster2>
Speicherzugriffsfehler

r.info raster2
D2/5: G__home home = /home/rusch
WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
WARNUNG: Kategorie Unterstützung für [raster2] im Mapset

[hohenems_site]

         missing
WARNUNG: Kann die History-Informationen der Karte [raster2] in

Mapset

         [hohenems_site] nicht finden.
WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht

lesen.

FEHLER: Kann die Wertespanne nicht lesen.

the problem appears on FC4,FC5 and FC6 aswell with following

configuration:

FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
--with-gdal=/usr/local/bin/gdal-config

--with-tcltk-includes=/usr/local/include

--with-postgres-includes=/usr/local/pgsql/include
--with-postgres-libs=/usr/local/pgsql/lib
--with-freetype-includes=/usr/include/freetype2

--with-freetype-libs=/usr/lib

--enable-largefile --with-odbc --with-motif --with-freetype=yes

--with-cxx

--with-glw --with-nls --with-blas --with-lapack
--with-lapack-libs=/usr/local/lib --with-ffmpeg
--with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
--with-proj-share=/usr/local/share/proj/ --enable-64bit

--with-python

i don't know which libs/pkg are used by g.copy; but i tried

different

versions

of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn;

tcl/tk8.5a5/tcl/tk8.4.14)

but it

seems to me that it's not dependent on a certain version of a

package.

thanks alot!
martin

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa

*

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

Martin Rutzinger wrote:

GRASS 6.3.cvs (utm):~ > gdb `which g.copy`

(gdb) run "rast=rott_one,test1"
Starting program: /usr/local/grass-6.3.cvs/bin/g.copy "rast=rott_one,test1"
[Thread debugging using libthread_db enabled]
[New Thread -1208944944 (LWP 13355)]
Copy <rott_one@hohenems_site> to current mapset as <test1>

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208944944 (LWP 13355)]
do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870 "hohenems_site",
new=0xa02b848 "test1") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb)

This looks like a problem with $GISBASE/etc/element_list.

--
Glynn Clements <glynn@gclements.plus.com>

Hi,

unfortunately I this moning made fresh checkout and compilation. It
happens also here, on i686 Gentoo with gcc version 4.1.1.

It looks like segfault happens at general/manage/lib/do_copy.c line 53
"if ( recursive_copy(path, path2) == 1 )" where function
recursive_copy returns zero. I'm not so deep in C and that module, but
it segfaulted after recursive_copy calls "return 0", so - error must
be somewhere there.

Maris.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1217730368 (LWP 6342)]
do_copy (n=0, old=0x8050398 "geology", mapset=0x8050420 "PERMANENT",
new=0x80503b0 "geol3") at do_copy.c:40
40 for (i = 0; i < list[n].nelem; i++)
(gdb) bt
#0 do_copy (n=0, old=0x8050398 "geology", mapset=0x8050420
"PERMANENT", new=0x80503b0 "geol3") at do_copy.c:40
#1 0x080495d3 in main (argc=2, argv=0xbf9157a4) at copy.c:80

2007/2/19, Sören Gebbert <soerengebbert@gmx.de>:

Hi,
i can not reproduce this error with the today's grass-CVS build on
Debian etch. The grass test suite produces no errors:

GRASS 6.3.cvs > ./RunGRASSTestSuite.sh -g

Start testing general (g.*) modules

g.copy test: success success success success finished
g.findfile test: success finished
g.filename test: success finished
g.remove test: success success success success success success
success success finished
g.rename test: success success success success success success
success success finished
g.proj output test: success success success success success
success success finished
g.tempfile test: success finished
g.gisenv test: success success finished
g.list test: success success success success success success
success success success success success finished
g.region output test: success success success success success
success success finished
g.version test: success success success finished

Finished testing general (g.*) modules

Soeren

Patton, Eric schrieb:
> Martin,
>
> I can confirm a segfault on using g.copy, with today's CVS on Ubuntu 6.06.
>
> g.copy exits with a segfault, but the maps seems to get copied to the
destination mapset as requested anyway. Only the command line run reaches a
segfault, not the GUI version. Or maybe the error just isn't visible from
the GUI.
>
> Output from gdb:
>
> $ gdb `which g.copy`
> GNU gdb 6.4-debian
> Copyright 2005 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
are
> welcome to change it and/or distribute copies of it under certain
conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
details.
> This GDB was configured as "i486-linux-gnu"...Using host libthread_db
library "/lib/tls/i686/cmov/libthread_db.so.1".
>
> (gdb) run rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
> Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
rast=Mispec_Apr2000.grd@UNB_Original_r4s,TEST_2
> [Thread debugging using libthread_db enabled]
> [New Thread -1224742304 (LWP 7624)]
> Copy <Mispec_Apr2000.grd@UNB_Original_r4s> to current mapset as <TEST_2>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1224742304 (LWP 7624)]
> 0xb7eda963 in G_strcasecmp (x=0x804d800 "cell", y=0x532d87 <Address
0x532d87 out of bounds>) at strings.c:146
> 146 while (*x && *y)
> (gdb)
>
> Devs, any other info needed to diagnose this error?
>
> ~ Eric.
>
> -----Original Message-----
> From: grass-dev-bounces@grass.itc.it
> To: Martin Landa
> Cc: grass-dev
> Sent: 2/19/2007 8:51 AM
> Subject: Re: [GRASS-dev] g.copy rast=
>
> GRASS 6.3.cvs (utm):~ > gdb `which g.copy`
>
> (gdb) run "rast=rott_one,test1"
> Starting program: /usr/local/grass-6.3.cvs/bin/g.copy
> "rast=rott_one,test1"
> [Thread debugging using libthread_db enabled]
> [New Thread -1208944944 (LWP 13355)]
> Copy <rott_one@hohenems_site> to current mapset as <test1>
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1208944944 (LWP 13355)]
> do_copy (n=0, old=0xa02b838 "rott_one", mapset=0xa02b870
> "hohenems_site",
> new=0xa02b848 "test1") at do_copy.c:40
> 40 for (i = 0; i < list[n].nelem; i++)
> (gdb)
>
> Zitat von Martin Landa <landa.martin@gmail.com>:
>
>> Hi,
>>
>> it is strange, on my machine g.copy works. What does gdb say?
>>
>> Martin
>>
>> 2007/2/19, Martin Rutzinger <Martin.Rutzinger@uibk.ac.at>:
>>> hi list,
>>>
>>> with the recent cvs version of grass63 g.copy for raster maps
> doesn't work
>> any
>>> more. i just get a meaningless 'memory access error'
>> (speicherzugriffsfehler).
>>> runinng configure, make, make install gives no error messages.
>>>
>>> g.gisenv set="DEBUG=5"
>>>
>>> g.copy rast=raster1,raster2
>>> D3/5: Copy rast
>>> Copy <raster1@hohenems_site> to current mapset as <raster2>
>>> Speicherzugriffsfehler
>>>
>>> r.info raster2
>>> D2/5: G__home home = /home/rusch
>>> WARNUNG: Kann Header-Datei [raster2 in hohenems_site] nicht öffnen
>>> WARNUNG: Kategorie Unterstützung für [raster2] im Mapset
> [hohenems_site]
>>> missing
>>> WARNUNG: Kann die History-Informationen der Karte [raster2] in
> Mapset
>>> [hohenems_site] nicht finden.
>>> WARNUNG: Kann range Datei für [raster2 in hohenems_site] nicht
> lesen.
>>> FEHLER: Kann die Wertespanne nicht lesen.
>>>
>>> the problem appears on FC4,FC5 and FC6 aswell with following
> configuration:
>>> FLAGS='-g -Wall' ./configure --with-x --enable-shared --with-proj
>>> --with-gdal=/usr/local/bin/gdal-config
>> --with-tcltk-includes=/usr/local/include
>>> --with-postgres-includes=/usr/local/pgsql/include
>>> --with-postgres-libs=/usr/local/pgsql/lib
>>> --with-freetype-includes=/usr/include/freetype2
>> --with-freetype-libs=/usr/lib
>>> --enable-largefile --with-odbc --with-motif --with-freetype=yes
> --with-cxx
>>> --with-glw --with-nls --with-blas --with-lapack
>>> --with-lapack-libs=/usr/local/lib --with-ffmpeg
>>> --with-ffmpeg-includes=/usr/local/include/ffmpeg --with-sqlite
>>> --with-proj-share=/usr/local/share/proj/ --enable-64bit
> --with-python
>>> i don't know which libs/pkg are used by g.copy; but i tried
> different
>> versions
>>> of e.g. gdal ( gdal-1.3.2/gdal-1.4.0/gdal-svn;
> tcl/tk8.5a5/tcl/tk8.4.14)
>> but it
>>> seems to me that it's not dependent on a certain version of a
> package.
>>> thanks alot!
>>> martin
>>>
>>> _______________________________________________
>>> grass-dev mailing list
>>> grass-dev@grass.itc.it
>>> http://grass.itc.it/mailman/listinfo/grass-dev
>>>
>>
>> --
>> Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa
> *
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev
>

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev