Re: [GRASS-dev] Nviz build (Grass70)

[Markus Neteler]

On Sat, Apr 10, 2010 at 11:36 AM, Massimo Di Stefano
 wrote:
>
> Tring to build Grass70 on debian sid (ffmeg installed from source svn)
> i get an error building Nviz, the same configure used to build grass65
> give me no errors and Nviz works fine on grass65.
>
>
> cd /usr/local/src/gis/grass_trunk/visualization/nviz
...
-lm  -ltcl8.5 -lm -lGLU  -lGL   -lSM -lICE -lX11 -lXmu -lXext  -lm  -lm
> /usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/lib/libgrass_ogsf.so:
>  undefined reference to `av_init_pac...@libavformat_52'
> collect2: ld returned 1 exit status
> make[1]: *** 
> [/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/bin/nviz]
> Error 1

Perhaps libgrass_ogsf.so and ffmeg are out of sync. Did you try
make distclean
?

Markus
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by sallar):

 Replying to [comment:8 hamish]:
 > ... and then type "bt full" at the (gdb) prompt after it breaks.
 >

 {{{
 (gdb) bt full
 #0  0xb7f8e424 in __kernel_vsyscall ()
 No symbol table info available.
 #1  0xb785a640 in raise () from /lib/i686/cmov/libc.so.6
 No symbol table info available.
 #2  0xb785c018 in abort () from /lib/i686/cmov/libc.so.6
 No symbol table info available.
 #3  0xb789734d in ?? () from /lib/i686/cmov/libc.so.6
 No symbol table info available.
 #4  0x0005 in ?? ()
 No symbol table info available.
 #5  0xbfffc6ac in ?? ()
 No symbol table info available.
 #6  0x0400 in ?? ()
 No symbol table info available.
 #7  0xbfffc9a8 in ?? ()
 No symbol table info available.
 #8  0xb7f72780 in G__read_Cell_head (fd=0x2, cellhd=0xb796d648,
 is_cellhd=-1073747515) at rd_cellhd.c:74
 count = 
 result = 0x400 
 array = (char **) 0x77722030
 buf = "-p b72c3000 00:00 0 \nb72c6000-b7309000 r-xp  03:03
 1354592/usr/lib/i686/cmov/libssl.so.0.9.8\nb7309000-b730d000 rw-p
 00042000 03:03
 }}}

 > did you install from pre-packaged binaries or self-compile? which linux
 distro/version? (smells like a recent ubuntu) If it's a binary install,
 where did you get the binaries from?
 >

 I installed grass by self-compile!
 My distro is Debian/lenny!

 > AFAICT the only thing it could be is this in g.proj/main.c,
 > {{{
 > if (projinfo != NULL)
 >   G_free_key_value(projinfo);
 > if (projunits != NULL)
 >   G_free_key_value(projunits);
 > }}}
 >
 >
 > but I'm not sure how that could happen as your debug message shows
 region proj:0. If you built from source could you try to rebuild, running
 "make distclean" before ./configure?
 >

 I rebuilt it but without success!

 >
 > Hamish

 thanks

 Salvatore

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [GRASS-user] How to embed a grass script (for example v.db.addcol) into a Pythonscript on windows?

[Michael Barton]

We tried starting GRASS in a dos window rather than msys using the command line 
option. This was a big improvement. We can run basic python scripts and start 
an interactive python session. So now we move on to new issues about running 
scripts.

1) scripts that call subprocess for some reason try to import threading which 
tries to import "collection". Collection does not exist. Very bizarre. Could 
this be a parser issue?

2) scripts that attempt to import the grass_script library cannot find it. 
Somehow this needs to get into the path/pythonpath at startup. 
$GISBASE/etc/python

Getting closer to python and GRASS in Windows.

Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice:  480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:  480-965-7671 SHESC),  480-727-0709 (CSDC)
www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu









On Apr 3, 2010, at 9:17 AM, Helmut Kudrnovsky wrote:

> Hi Michael,
> 
> at the moment the WinGrass64-Installer ships it's own copy of python/wxpython 
> (installed in C:\Program Files\GRASS-64-SVN\Python25). 
> In the starting scripts (grass64.bat, Init.bat) the path to this python-copy 
> is set.
> 
> the wingrass-installer adds in the windows-start-menue "GRASS Command Line". 
> this starts Grass64 in text mode in a normal Windows-console (not in rxvt), 
> but you can start the wxgui from this Windows-console inside a grass-session 
> by the command "g.gui wxpython".
> 
> and in this windows-console with the grass-session you have access to the 
> wingrass-python-copy (installed in C:\Program Files\GRASS-64-SVN\Python25). 
> for example you can start python inside a grass-session.
> 
> maybe this could be a starting point for testing python-scripting in 
> wingrass64?
> 
> best regards
> Helmut
> 
> -
> Von: Michael Barton 
> Gesendet: 03.04.2010 01:14:31
> An: "Colin (Nielsen) Wren" ,Helmut Kudrnovsky 
> 
> Betreff: Fwd: [GRASS-dev] Fwd: [GRASS-user] How to embed a grass script (for 
> example v.db.addcol) into a Pythonscript on windows?
> 
> 
> Colin and Helmut,
> 
> Is there some way that these suggestions can be implemented as default 
> behavior in GRASS for Windows, or at least as an option? It is important that 
> we can run scripts from Windows. Unfortunately, I don't understand this 
> completely at the moment, but hope to test it out with students to get a 
> clearer idea of how it all works.
> 
> Michael
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> __
> C. Michael Barton 
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
> 
> 
> voice:  480-965-6262 (SHESC), 480-727-9746 (CSDC)
> fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
> www:  [http://csdc.asu.edu], [http://shesc.asu.edu]
> [http://www.public.asu.edu/~cmbarton]
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Begin forwarded message:
> 
> 
> 
> From: Glynn Clements <[gl...@gclements.plus.com]>
> 
> Date: April 2, 2010 3:54:22 PM MST
> 
> To: Michael Barton <[michael.bar...@asu.edu]>
> 
> Cc: Isaac Ullah <[isaac.ul...@asu.edu]>, Andrea Torvinen 
> <[atorv...@asu.edu]>, GRASS developers grass-developers 
> <[grass-...@lists.osgeo.org]>
> 
> Subject: Re: [GRASS-dev] Fwd: [GRASS-user] How to embed a grass script (for 
> example v.db.addcol) into a Pythonscript on windows?
> 
> 
> 
> 
> Michael Barton wrote:
> 
> 
> OK. This helps. We were trying it in the "MSys' (broken and deprecated)
> 
> rxvt program".
> 
> 
> 
> Like I said, I'm not familiar enough with Windows to realize that this
> 
> would not work. I'm trying to help get python GRASS scripts to work
> 
> under Windows. So testing it from MSys is not the way to go. Should we
> 
> just try running a python script from the wxpython command prompt? Or
> 
> should we do it from the MSys prompt?
> 
> 
> First, I would suggest using the batch file which I posted (or
> something quite similar) to start a session using cmd.exe in a Windows
> console.
> 
> For running a *script*, it shouldn't matter whether you use rxvt or a
> console, but it will matter for running Python interactively. Using
> bash might cause problems, so it's best to avoid that at first.
> 
> 
> Is there a shebang that we should be using on Windows that is different
> 
> from the stock one (#!/usr/bin/env python). 
> 
> 
> Shebangs don't work with Windows; that's a feature of MSys' bash.
> Windows uses the extension.
> 
> If you've installed Python using the stock .msi installer from
> [python.org], it should have associated the .py extension with the
> python.file type, and the python.file type with something like:
> 
> "C:\Python26\python.exe" "%1" %*
> 
> 
> I'm looking for a cookbook approach that I can tell to students and
> 
> other who would like

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by hamish):

 ... and then type "bt full" at the (gdb) prompt after it breaks.

 did you install from pre-packaged binaries or self-compile? which linux
 distro/version? (smells like a recent ubuntu) If it's a binary install,
 where did you get the binaries from?

 AFAICT the only thing it could be is this in g.proj/main.c,
 {{{
 if (projinfo != NULL)
 G_free_key_value(projinfo);
 if (projunits != NULL)
 G_free_key_value(projunits);
 }}}


 but I'm not sure how that could happen as your debug message shows region
 proj:0. If you built from source could you try to rebuild, running "make
 distclean" before ./configure?


 Hamish

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by sallar):

 Replying to [comment:6 martinl]:

 > Please run
 >
 > {{{
 > gdb g.proj
 > run -p
 > }}}
 >
 > instead.

 I get this:

 {{{
 GRASS 6.4.0RC6 (PIT):~ > gdb g.proj
 GNU gdb 6.8-debian
 Copyright (C) 2008 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later
 
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
 and "show warranty" for details.
 This GDB was configured as "i486-linux-gnu"...
 (gdb) run -p
 Starting program: /usr/local/grass-6.4.0RC6/bin/g.proj -p
 [Thread debugging using libthread_db enabled]
 D2/5: G__read_Cell_head
 D2/5: G__read_Cell_head_array
 D3/5: region item: proj:   0
 D3/5: region item: zone:   0
 D3/5: region item: north:  4526334.08251007
 D3/5: region item: south:  4474101.25111007
 D3/5: region item: east:   563815.12526504
 D3/5: region item: west:   528349.01576504
 D3/5: region item: cols:   20
 D3/5: region item: rows:   20
 D3/5: region item: e-w resol:  1773.305475
 D3/5: region item: n-s resol:  2611.64157
 D3/5: region item: top:1
 D3/5: region item: bottom: 0
 D3/5: region item: cols3:  20
 D3/5: region item: rows3:  20
 D3/5: region item: depths: 1
 D3/5: region item: e-w resol3: 1773.305475
 D3/5: region item: n-s resol3: 2611.64157
 D3/5: region item: t-b resol:  1
 XY location (unprojected)
 *** glibc detected *** /usr/local/grass-6.4.0RC6/bin/g.proj: double free
 or corruption (fasttop): 0x0804e510 ***
 [New Thread 0xb6e036d0 (LWP 10727)]
 === Backtrace: =
 /lib/i686/cmov/libc.so.6[0xb7802624]
 /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb7804826]
 /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb74802e1]
 /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xb745cb2d]
 /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x51)[0xb745e501]
 /lib/i686/cmov/libc.so.6(__cxa_finalize+0xc1)[0xb77c2e51]
 /usr/lib/libgeos-3.1.0.so[0xb72d4dc4]
 /usr/lib/libgeos-3.1.0.so[0xb737dcd0]
 /lib/ld-linux.so.2[0xb7f02453]
 /lib/i686/cmov/libc.so.6(exit+0x89)[0xb77c2ab9]
 /usr/local/grass-6.4.0RC6/bin/g.proj(main+0x3d2)[0x804a7d2]
 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb77aa455]
 /usr/local/grass-6.4.0RC6/bin/g.proj[0x8049a21]
 === Memory map: 
 08048000-0804c000 r-xp  03:03 1164337
 /usr/local/grass-6.4.0RC6/bin/g.proj
 0804c000-0804d000 rw-p 4000 03:03 1164337
 /usr/local/grass-6.4.0RC6/bin/g.proj
 0804d000-0806e000 rw-p 0804d000 00:00 0  [heap]
 b6d0-b6d21000 rw-p b6d0 00:00 0
 b6d21000-b6e0 ---p b6d21000 00:00 0
 b6e03000-b6e06000 rw-p b6e03000 00:00 0
 b6e06000-b6e6c000 r-xp  03:03 819183
 /usr/lib/libgcrypt.so.11.4.4
 b6e6c000-b6e6e000 rw-p 00066000 03:03 819183
 /usr/lib/libgcrypt.so.11.4.4
 b6e6e000-b6e71000 r-xp  03:03 818510 /usr/lib/libgpg-
 error.so.0.3.0
 b6e71000-b6e72000 rw-p 2000 03:03 818510 /usr/lib/libgpg-
 error.so.0.3.0
 b6e72000-b6e81000 r-xp  03:03 818452
 /usr/lib/libtasn1.so.3.0.15
 b6e81000-b6e82000 rw-p e000 03:03 818452
 /usr/lib/libtasn1.so.3.0.15
 b6e82000-b6f19000 r-xp  03:03 818764
 /usr/lib/libgnutls.so.26.4.6
 b6f19000-b6f1f000 rw-p 00097000 03:03 818764
 /usr/lib/libgnutls.so.26.4.6
 b6f1f000-b6f2 rw-p b6f1f000 00:00 0
 b6f2-b6f36000 r-xp  03:03 817192
 /usr/lib/libsasl2.so.2.0.22
 b6f36000-b6f37000 rw-p 00015000 03:03 817192
 /usr/lib/libsasl2.so.2.0.22
 b6f37000-b6f43000 r-xp  03:03 817395
 /usr/lib/liblber-2.4.so.2.1.0
 b6f43000-b6f44000 rw-p c000 03:03 817395
 /usr/lib/liblber-2.4.so.2.1.0
 b6f44000-b6f54000 r-xp  03:03 51464
 /lib/i686/cmov/libresolv-2.7.so
 b6f54000-b6f56000 rw-p f000 03:03 51464
 /lib/i686/cmov/libresolv-2.7.so
 b6f56000-b6f58000 rw-p b6f56000 00:00 0
 b6f58000-b6f5a000 r-xp  03:03 32806  /lib/libkeyutils-1.2.so
 b6f5a000-b6f5b000 rw-p 1000 03:03 32806  /lib/libkeyutils-1.2.so
 b6f5b000-b6f62000 r-xp  03:03 277767
 /usr/lib/libkrb5support.so.0.1
 b6f62000-b6f63000 rw-p 6000 03:03 277767
 /usr/lib/libkrb5support.so.0.1
 b6f63000-b6f64000 rw-p b6f63000 00:00 0
 b6f64000-b6f87000 r-xp  03:03 277757
 /usr/lib/libk5crypto.so.3.1
 b6f87000-b6f88000 rw-p 00023000 03:03 277757
 /usr/lib/libk5crypto.so.3.1
 b6f88000-b6f9d000 r-xp  03:03 51453
 /lib/i686/cmov/libpthread-2.7

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by martinl):

 Replying to [comment:5 sallar]:
 > Replying to [comment:3 hamish]:
 > > could you run with DEBUG level set to 5?
 > >  g.gisenv set="DEBUG=5"
 >
 > ok, I set the debug level to 5! then
 >
 > > could you post a gdb backtrace?
 > >  http://grass.osgeo.org/wiki/Bugs#Using_GDB
 {{{
 > GRASS 6.4.0RC6 (PIT):~ > gdb g.gui
 }}}

 Please run

 {{{
 gdb g.proj
 run -p
 }}}

 instead.

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by sallar):

 Replying to [comment:3 hamish]:
 > could you run with DEBUG level set to 5?
 >  g.gisenv set="DEBUG=5"

 ok, I set the debug level to 5! then

 > could you post a gdb backtrace?
 >  http://grass.osgeo.org/wiki/Bugs#Using_GDB
 >
 ..

 {{{
 GRASS 6.4.0RC6 (PIT):~ > gdb g.gui
 GNU gdb 6.8-debian
 Copyright (C) 2008 Free Software Foundation, Inc.
 License GPLv3+: GNU GPL version 3 or later
 
 This is free software: you are free to change and redistribute it.
 There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
 and "show warranty" for details.
 This GDB was configured as "i486-linux-gnu"...
 (gdb) run
 Starting program: /usr/local/grass-6.4.0RC6/bin/g.gui
 D1/5: Attempting to start 'wxpython' GUI ...
 Error: Reading settings from file  failed.
Details: need more than 1 value to unpack
Line: 'profile:raster2:pstyle:solid:pwidth:1:pcolor:(0, 255, 0,
 255)'
 Error: Reading settings from file  failed.
Details: need more than 1 value to unpack
Line: 'profile:raster2:pstyle:solid:pwidth:1:pcolor:(0, 255, 0,
 255)'
 *** glibc detected *** g.proj: double free or corruption (fasttop):
 0x0804e510 ***
 === Backtrace: =
 /lib/i686/cmov/libc.so.6[0xb784a624]
 /lib/i686/cmov/libc.so.6(cfree+0x96)[0xb784c826]
 /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb74c82e1]
 /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xb74a4b2d]
 /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x51)[0xb74a6501]
 /lib/i686/cmov/libc.so.6(__cxa_finalize+0xc1)[0xb780ae51]
 /usr/lib/libgeos-3.1.0.so[0xb731cdc4]
 /usr/lib/libgeos-3.1.0.so[0xb73c5cd0]
 /lib/ld-linux.so.2[0xb7f4a453]
 /lib/i686/cmov/libc.so.6(exit+0x89)[0xb780aab9]
 g.proj(main+0x3d2)[0x804a7d2]
 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb77f2455]
 g.proj[0x8049a21]
 === Memory map: 
 08048000-0804c000 r-xp  03:03 1164337
 /usr/local/grass-6.4.0RC6/bin/g.proj
 0804c000-0804d000 rw-p 4000 03:03 1164337
 /usr/local/grass-6.4.0RC6/bin/g.proj
 0804d000-0806e000 rw-p 0804d000 00:00 0  [heap]
 b6d0-b6d21000 rw-p b6d0 00:00 0
 b6d21000-b6e0 ---p b6d21000 00:00 0
 b6e4b000-b6e4e000 rw-p b6e4b000 00:00 0
 b6e4e000-b6eb4000 r-xp  03:03 819183
 /usr/lib/libgcrypt.so.11.4.4
 b6eb4000-b6eb6000 rw-p 00066000 03:03 819183
 /usr/lib/libgcrypt.so.11.4.4
 b6eb6000-b6eb9000 r-xp  03:03 818510 /usr/lib/libgpg-
 error.so.0.3.0
 b6eb9000-b6eba000 rw-p 2000 03:03 818510 /usr/lib/libgpg-
 error.so.0.3.0
 b6eba000-b6ec9000 r-xp  03:03 818452
 /usr/lib/libtasn1.so.3.0.15
 b6ec9000-b6eca000 rw-p e000 03:03 818452
 /usr/lib/libtasn1.so.3.0.15
 b6eca000-b6f61000 r-xp  03:03 818764
 /usr/lib/libgnutls.so.26.4.6
 b6f61000-b6f67000 rw-p 00097000 03:03 818764
 /usr/lib/libgnutls.so.26.4.6
 b6f67000-b6f68000 rw-p b6f67000 00:00 0
 b6f68000-b6f7e000 r-xp  03:03 817192
 /usr/lib/libsasl2.so.2.0.22
 b6f7e000-b6f7f000 rw-p 00015000 03:03 817192
 /usr/lib/libsasl2.so.2.0.22
 b6f7f000-b6f8b000 r-xp  03:03 817395
 /usr/lib/liblber-2.4.so.2.1.0
 b6f8b000-b6f8c000 rw-p c000 03:03 817395
 /usr/lib/liblber-2.4.so.2.1.0
 b6f8c000-b6f9c000 r-xp  03:03 51464
 /lib/i686/cmov/libresolv-2.7.so
 b6f9c000-b6f9e000 rw-p f000 03:03 51464
 /lib/i686/cmov/libresolv-2.7.so
 b6f9e000-b6fa rw-p b6f9e000 00:00 0
 b6fa-b6fa2000 r-xp  03:03 32806  /lib/libkeyutils-1.2.so
 b6fa2000-b6fa3000 rw-p 1000 03:03 32806  /lib/libkeyutils-1.2.so
 b6fa3000-b6faa000 r-xp  03:03 277767
 /usr/lib/libkrb5support.so.0.1
 b6faa000-b6fab000 rw-p 6000 03:03 277767
 /usr/lib/libkrb5support.so.0.1
 b6fab000-b6fac000 rw-p b6fab000 00:00 0
 b6fac000-b6fcf000 r-xp  03:03 277757
 /usr/lib/libk5crypto.so.3.1
 b6fcf000-b6fd rw-p 00023000 03:03 277757
 /usr/lib/libk5crypto.so.3.1
 b6fd-b6fe5000 r-xp  03:03 51453
 /lib/i686/cmov/libpthread-2.7.so
 b6fe5000-b6fe7000 rw-p 00014000 03:03 51453
 /lib/i686/cmov/libpthread-2.7.so
 b6fe7000-b6fe9000 rw-p b6fe7000 00:00 0
 b6fe9000-b7029000 r-xp  03:03 817426
 /usr/lib/libldap_r-2.4.so.2.1.0
 b7029000-b702b000 rw-p 0003f000 03:03 817426
 /usr/lib/libldap_r-2.4.so.2.1.0
 b702b000-b702c000 rw-p b702b000 00:00 0
 b702c000-b7035000 r-xp  03:03 50035
 /lib/i686/cmov/libcrypt-2.7.so
 b7035000-b7037000 rw-p 8000 03:03 50035
 /lib/i686/cmov/li

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  default  | Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Changes (by martinl):

  * component:  wxGUI => default

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  wxGUI| Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by hamish):

 could you run with DEBUG level set to 5?
  g.gisenv set="DEBUG=5"


 could you post a gdb backtrace?
  http://grass.osgeo.org/wiki/Bugs#Using_GDB


 Hamish

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  wxGUI| Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Comment (by sallar):

 Replying to [comment:1 martinl]:
 > Please try to run
 >
 > {{{
 > g.proj -p
 > }}}
 >
 > What is says?

 This is part of the output:

 {{{
 GRASS 6.4.0RC6 (PIT):~ > g.proj -p
 XY location (unprojected)
 *** glibc detected *** g.proj: double free or corruption (fasttop):
 0x0804e510 ***

 }}}

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
  Reporter:  sallar   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  blocker  |   Milestone:  6.4.0
 Component:  wxGUI| Version:  6.4.0 RCs
Resolution:   |Keywords:  g.proj   
  Platform:  Linux| Cpu:  x86-32   
--+-
Changes (by martinl):

  * keywords:  g.proj,wxGUI => g.proj

Comment:

 Please try to run

 {{{
 g.proj -p
 }}}

 What is says?

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] 6.4.0 blocker bugs

[Martin Landa]

Hi,

2010/4/10 Glynn Clements :

> 6.4.0 should be sync'd to 6.5. Maybe 6.5 should be sync'd to 7.0
> first, with one exception: the 7.0 version of grass.script.mapcalc()

6.5 sync'ed with 7.0 in r41773, after some testing can be backported to 6.4.

Martin

-- 
Martin Landa  * http://gama.fsv.cvut.cz/~landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS GIS] #1006: r.terraflow fails to stat() stream file on Windows

[GRASS GIS]

#1006: r.terraflow fails to stat() stream file on Windows
--+-
  Reporter:  marisn   |   Owner:  grass-dev@lists.osgeo.org
  Type:  defect   |  Status:  new  
  Priority:  critical |   Milestone:  6.4.0
 Component:  Raster   | Version:  svn-releasebranch64  
Resolution:   |Keywords:  wingrass, r.terraflow
  Platform:  MSWindows Vista  | Cpu:  x86-32   
--+-
Changes (by hamish):

  * keywords:  wxgui, wingrass, terraflow => wingrass, r.terraflow

Comment:

 - removed wxgui keyword, it also happens from the msys prompt.


 Maris: fyi extra debug messages only added in 6.5svn.
 {{{
 STREAM temporary files in C:/Users/Maris/AppData/Local/Temp
 ...
 stats.out: Permission denied
 }}}

 stats.out tries to write to the current working directory, try running
  cd C:/Users/Maris/AppData/Local/Temp
 or your home dir before starting the program. (or change the stats=
 filename option)

 (IIUC stats.out file just contains extra debug messages; STREAM is a copy
 of the raster map stored on disk for random access)


 testing with the latest 6.5 nightly wingrass build (r41761), it looks like
 the stat() on an open file is in fact the problem:

 {{{
 #spearfish
 g.region rast=elevation.dem
 r.terraflow ele=elevation.dem filled=rterra.fill dir=rterra.dir \
   swat=rterra.swat acc=rterra.acc tci=rterra.tci mem=600
 ...
 D3/3: create window mapping (633 columns)
 C:/DOCUME~1/OPG/LOCALS~1/Temp/STREAM_a03788: length = 0   sizeof(T)=4
 D3/3: nrows=466   ncols=633stream_len()=0
 C:/DOCUME~1/OPG/LOCALS~1/Temp/STREAM_a03788: length = 0   sizeof(T)=4
 Assertion failed: nrows * ncols == str->stream_len(), file grass2str.h,
 line 146

 # file size on disk:
 wc -c C:/DOCUME~1/OPG/LOCALS~1/Temp/STREAM_a03788
 1179912
 }}}

 {{{
 633*466 = 294978 cells
 1179912 / 294978 = 4 bytes per cell
 }}}


 Hamish

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Nviz build (Grass70)

[Massimo Di Stefano]

Tring to build Grass70 on debian sid (ffmeg installed from source svn)
i get an error building Nviz, the same configure used to build grass65 
give me no errors and Nviz works fine on grass65.


cd /usr/local/src/gis/grass_trunk/visualization/nviz
 make
make -C src
make[1]: Entering directory 
`/usr/local/src/gis/grass_trunk/visualization/nviz/src'
: && gcc -L/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/lib 
-L/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/lib 
-Wl,--export-dynamic 
-Wl,-rpath-link,/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/lib
   -o /usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/bin/nviz 
OBJ.x86_64-unknown-linux-gnu/anim_support.o 
OBJ.x86_64-unknown-linux-gnu/change_view.o 
OBJ.x86_64-unknown-linux-gnu/cutplane_obj.o 
OBJ.x86_64-unknown-linux-gnu/do_zoom.o OBJ.x86_64-unknown-linux-gnu/draw.o 
OBJ.x86_64-unknown-linux-gnu/exag.o OBJ.x86_64-unknown-linux-gnu/glwrappers.o 
OBJ.x86_64-unknown-linux-gnu/init_commands.o 
OBJ.x86_64-unknown-linux-gnu/label.o OBJ.x86_64-unknown-linux-gnu/lights.o 
OBJ.x86_64-unknown-linux-gnu/map_obj.o OBJ.x86_64-unknown-linux-gnu/misc.o 
OBJ.x86_64-unknown-linux-gnu/nvizAppInit.o 
OBJ.x86_64-unknown-linux-gnu/nviz_init.o 
OBJ.x86_64-unknown-linux-gnu/nvizMain.o 
OBJ.x86_64-unknown-linux-gnu/pick_vect_commands.o 
OBJ.x86_64-unknown-linux-gnu/position.o 
OBJ.x86_64-unknown-linux-gnu/query_vect.o 
OBJ.x86_64-unknown-linux-gnu/quick_draw.o 
OBJ.x86_64-unknown-linux-gnu/script_support.o 
OBJ.x86_64-unknown-linux-gnu/togl.o OBJ.x86_64-unknown-linux-gnu/togl_cb.o 
OBJ.x86_64-unknown-linux-gnu/togl_flythrough.o 
OBJ.x86_64-unknown-linux-gnu/volume.o-lgrass_ogsf -lgrass_bitmap 
-lgrass_linkm -lgrass_vector -lgrass_dig2 -lgrass_dgl -lgrass_rtree 
-lgrass_linkm -lgrass_dbmiclient -lgrass_dbmibase  -lgrass_sites -lgrass_form 
-lgrass_dbmiclient -lgrass_dbmibase  -lgrass_g3d -lgrass_gis -lgrass_datetime  
-ltiff  -ltk8.5 -lm  -ltcl8.5 -lm -lGLU  -lGL   -lSM -lICE -lX11 -lXmu -lXext  
-lm  -lm  
/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/lib/libgrass_ogsf.so:
 undefined reference to `av_init_pac...@libavformat_52'
collect2: ld returned 1 exit status
make[1]: *** 
[/usr/local/src/gis/grass_trunk/dist.x86_64-unknown-linux-gnu/bin/nviz] Error 1
make[1]: Leaving directory 
`/usr/local/src/gis/grass_trunk/visualization/nviz/src'
make: *** [default] Error 2


thanks!

Massimo.___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Query vector in edit mode

[Massimo Di Stefano]

Hi All,

using grass65 svn, when i query a vector in "Edit mode" and the zoom level is 
not "appropriate"
(eg.: zoom too out -> mouse pick detect more than one feature, as when we have 
too dense points)

i have this error :


Traceback (most recent call last):
  File "/usr/local/src/gis/grass6_devel/dist.x86_64-unknown-
linux-gnu/etc/wxpython/gui_modules/mapdisp_window.py", line
1077, in MouseActions

self.OnLeftUp(event)
  File "/usr/local/src/gis/grass6_devel/dist.x86_64-unknown-
linux-gnu/etc/wxpython/gui_modules/mapdisp_window.py", line
1886, in OnLeftUp

self.parent.QueryVector(self.mouse['begin'][0],
self.mouse['begin'][1])
  File "/usr/local/src/gis/grass6_devel/dist.x86_64-unknown-
linux-gnu/etc/wxpython/gui_modules/mapdisp.py", line 1477,
in QueryVector

action="update")
  File "/usr/local/src/gis/grass6_devel/dist.x86_64-unknown-
linux-gnu/etc/wxpython/gui_modules/dbm_dialogs.py", line
106, in __init__

self.UpdateDialog(query=query, cats=cats)
  File "/usr/local/src/gis/grass6_devel/dist.x86_64-unknown-
linux-gnu/etc/wxpython/gui_modules/dbm_dialogs.py", line
343, in UpdateDialog

tfid = int(data['Id'][idx])
IndexError
:
list index out of range
 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #1032: ErrorCommandExecution g.proj

[GRASS GIS]

#1032: ErrorCommandExecution g.proj
--+-
 Reporter:  sallar|   Owner:  grass-dev@lists.osgeo.org
 Type:  defect|  Status:  new  
 Priority:  blocker   |   Milestone:  6.4.0
Component:  wxGUI | Version:  6.4.0 RCs
 Keywords:  g.proj,wxGUI  |Platform:  Linux
  Cpu:  x86-32|  
--+-
 By starting with grass wxgui, hangs with the following error [1][[BR]]

 In the shell appears as follows:


 {{{
 File "/usr/local/grass-6.4.0RC6/etc/wxpython/gui_modules/wxgui_utils.py",
 line 84, in __init__
 self.Map = render.Map()# instance of render.Map to be associated
 with display
   File "/usr/local/grass-6.4.0RC6/etc/wxpython/gui_modules/render.py",
 line 402, in __init__
 self.projinfo = self.ProjInfo()
   File "/usr/local/grass-6.4.0RC6/etc/wxpython/gui_modules/render.py",
 line 765, in ProjInfo
 p = gcmd.Command(['g.proj', '-p'])
   File "/usr/local/grass-6.4.0RC6/etc/wxpython/gui_modules/gcmd.py", line
 369, in __init__
 _("Error: ") + self.GetError()))
 gui_modules.gcmd.CmdError
 }}}


 [1]-http://www.filedropper.com/errorincommandexecutiongproj

-- 
Ticket URL: 
GRASS GIS 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] nviz: overlay two color raster maps?

[Hamish]

Markus wrote:
> Masking in NVIZ didn't have to seem an effect.
> 
> Any ideas?

Yeah, make a surface attributes mask & transparency map but with
values of 255 not 0/null. It's a bit of a pain but I've made
this work in the past. It seems like the sort of trick I would
have instantly added to the wiki/man page/ML, but I don't see
it right now (I only had a very quick look).

mmm. coming back to me now. have a look around bug #111 r.los
on WinGrass- with a 3D view of visibility from a spot in an
Italian valley draped over LANDSAT. screenshot is dated 1/1/10:
http://bambi.otago.ac.nz/hamish/grass/bugs/rlos_onearth.jpg

r.mapcalc rlos255 = "if(isnull(rlos), 255, rlos)"

I've still got the nviz state file and mapset's .bash_history
if you are still stuck & want to try and recreate what I did.

cut from the nviz state file:

7 7
1 1
poly
grid_wire
gouraud
surf*1262344157
map d...@permanent
0
map r...@paolo
0
map rlos...@paolo
0
map rlos...@paolo
const 60.00
unset
#88
0.00 0.00 5.00


ah, ok, that is a second raster surface added 5m above the
landsat DTM.

let me know if you are still stuck and I'll package up the
mapset as a tarball as an example.


Hamish



  
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev