[Xotcl] how to track a segmentation fault problem in Xotcl?

Catherine Letondal letondal at pasteur.fr
Mon Sep 1 16:18:02 CEST 2003


Zoran Vasiljevic wrote:
> On Monday 01 September 2003 11:56, Catherine Letondal wrote:
> >
> > > You should compile wish with symbols (./configure --enable-symbols).
> > > The same appiles for xotcl as well.
> >
> > When I compile xotcl after a ./configure --enable-symbols the compilation
> > just fails to compile because it looks for a libtcl8.3g.so file (or maybe I
> > should have built the tcl library before?):
> 
> Of course, you need to compile Tcl with --enable-symbols. 
> This will produce the libtcl8.3g.so library.
> 
> > I don't remember how it is I still have a libxotcl1.o.so built!!
> >
> > No wonder there is a segmentation fault.
> >
> > Thanks a lot for any help,
> 
> No problem. Just get a clean compilation of xotcl first.
> If the problems persist, then recompile all with --enable-symbols
> and give it another try. 
> 

Ok: everything is recompiled with --enable-symbols and the compilation of Xotcl
went without pbs.
I still have the seg fault:

% gdb ~/Work/TclTk/proto/mywish2/mywish core
GNU gdb 4.18
Copyright 1998 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 "sparc-sun-solaris2.7"...
Core was generated by `/home/letondal/Work/TclTk/proto/mywish2/mywish'.
Program terminated with signal 9, Killed.
Reading symbols from /local/lib/libGLU.so.1...done.
Reading symbols from /local/lib/libGL.so.1...done.
Reading symbols from /local/lib/libglut.so.3...done.
Reading symbols from /home/letondal/packages/seqiotcl/seqiotcl.so...done.
Reading symbols from /local/lib/libxotcl1.0g.so...done.
Reading symbols from /local/lib/libtk8.3.so...done.
Reading symbols from /local/lib/libtcl8.3g.so...done.
Reading symbols from /usr/lib/libX11.so.4...done.
Reading symbols from /usr/lib/libm.so.1...done.
Reading symbols from /usr/lib/libc.so.1...done.
Reading symbols from /usr/openwin/lib/libSM.so.6...done.
Reading symbols from /usr/openwin/lib/libICE.so.6...done.
Reading symbols from /usr/openwin/lib/libXmu.so.4...done.
Reading symbols from /usr/openwin/lib/libXext.so.0...done.
Reading symbols from /usr/openwin/lib/libXi.so.5...done.
Reading symbols from /usr/lib/libpthread.so.1...done.
Reading symbols from /local/lib/libtcl8.2.so...done.
Reading symbols from /usr/lib/libsocket.so.1...done.
Reading symbols from /usr/lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libdl.so.1...done.
Reading symbols from /usr/openwin/lib/libXt.so.4...done.
---Type <return> to continue, or q <return> to quit---
Reading symbols from /usr/lib/libmp.so.2...done.
Reading symbols from /usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1...done.
Reading symbols from /usr/lib/libthread.so.1...done.
Reading symbols from /home/letondal/Work/TclTk/proto/iMol/iMol.so...done.
Reading symbols from /home/letondal/Work/TclTk/proto/i3DMol/lib/i3D.so...done.
#0  Tcl_PopCallFrame (interp=0x19c380) at ./../generic/tclNamesp.c:359
359         iPtr->framePtr = framePtr->callerPtr;
(gdb) l
354          * of call frames before deleting local variables, so that traces
355          * invoked by the variable deletion don't see the partially-deleted
356          * frame.
357          */
358
359         iPtr->framePtr = framePtr->callerPtr;
360         iPtr->varFramePtr = framePtr->callerVarPtr;
361
362         /*
363          * Delete the local variables. As a hack, we save then restore the



Any idea about the problem?

Thanks a lot in advance,

--
Catherine Letondal



More information about the Xotcl mailing list