Re: error on start up compiled cvs version



On Wed, 2005-04-06 at 09:42 +0100, Denny Beyer wrote:
Lars Clausen wrote:
On Tue, 2005-04-05 at 16:56 +0100, Denny Beyer wrote:
 
Hello !
After updating the cvs of dia located in my home-directory and following 
the autogen -compile- make instructions i encounter the following 
problem (German):
./app/run_dia.sh: line 22: 18973 Speicherzugriffsfehler  
"$DIA_APP_PATH/dia" "$@"
which means more or less: Memory access error.
Another previous cvs snapshot, where I did some alterings on, works 
(located in another directory next to this one).

The run_dia.sh files are the same.

Any idea how to fix that?
   

I haven't seen anything like that enter CVS, and I can't tell more from
the info you give here.

If you export DEBUGGER=gdb before you app/run_dia.sh, you can get more
debugging info out.  Just do run, then when (if) it crashes, do bt.
 
<gdb>

(gdb) run app/run_dia.sh
Starting program: /home/denny/devel/dia-cvs/app/.libs/lt-dia app/run_dia.sh
[Thread debugging using libthread_db enabled]
[New Thread 1084073856 (LWP 10352)]
Detaching after fork from child process 10355.
Detaching after fork from child process 10356.

** (lt-dia:10352): WARNING **: No valid configuration files found for 
the XSLT plugin, not loading.

** (lt-dia:10352): WARNING **: Python: Couldn't find startup file 
/usr/local/share/dia/python-startup.py


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1084073856 (LWP 10352)]
0x40627fa2 in g_type_check_instance_cast () from 
/opt/gnome/lib/libgobject-2.0.so.0
(/gdb)

Then the program terminates. Any idea whats going on?

You don't want to do run app/run_dia.sh inside gdb, rather set DEBUGGER
to gdb and then run app/run_dia.sh.  For example:

larsrc linux:~/dia> export DEBUGGER=gdb
larsrc linux:~/dia> app/run_dia.sh
GNU gdb 6.2.1
Copyright 2004 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 "i586-suse-linux"...Using host libthread_db
library "/lib/tls/libthread_db.so.1".
 
(gdb) run
....<output>...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1084082688 (LWP 28150)]
0xffffe410 in ?? ()
(gdb) bt
...<interesting output>...
-Lars

-- 
Lars Clausen <lars raeder dk>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]