Markus Neteler schrieb am Mo., 30. Juli 2018, 13:37:
> Hi again,
>
> On Mon, Jul 30, 2018 at 1:05 PM, Markus Neteler wrote:
> ...
> > Thread 1 "python" received signal SIGSEGV, Segmentation fault.
> > 0x7fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
> > (gdb) bt full
> > #0
On Mon, Jul 30, 2018 at 1:37 PM, Markus Neteler wrote:
>
> Hi again,
>
> On Mon, Jul 30, 2018 at 1:05 PM, Markus Neteler wrote:
> ...
> > Thread 1 "python" received signal SIGSEGV, Segmentation fault.
> > 0x7fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
> > (gdb) bt full
> > #
Hi again,
On Mon, Jul 30, 2018 at 1:05 PM, Markus Neteler wrote:
...
> Thread 1 "python" received signal SIGSEGV, Segmentation fault.
> 0x7fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
> (gdb) bt full
> #0 0x7fffd7ac305b in blas_shutdown () from /lib64/libopenblaso.so.0
>
Hi again,
On Mon, Jul 30, 2018 at 12:33 PM, Markus Neteler wrote:
...
> So the segfault happens when t.list (or other t.* scripts) close.
>
> ?
Now using gdb to debug the script (and G74svn recompiled from scratch):
GRASS 7.4.2svn (nc_spm_08_grass7):~/software/grass74 > gdb python
GNU gdb (GDB)
On Sat, Jul 28, 2018 at 11:40 PM, Veronica Andreo wrote:
> Hi devs,
>
> I get "segmentation fault" when running temporal commands, i.e., t.list,
> t.info, t.create, t.register (haven't tested them all). However, the command
> works as expected. It's just that I get the message "Segmentation fault
Hi devs,
I get "segmentation fault" when running temporal commands, i.e., t.list,
t.info, t.create, t.register (haven't tested them all). However, the
command works as expected. It's just that I get the message "Segmentation
fault (core dumped)" whenever I run a temporal command. I use grass trunk
