[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
segmentation fault maybe from Tcl
From: |
Andreas Wegerich |
Subject: |
segmentation fault maybe from Tcl |
Date: |
Wed, 12 Dec 2001 14:39:31 +0100 |
Hello,
I work with swarm (2.1.1) since a few months. It works fine until our Linux
was updated. Now there's a segmentation fault immediately after starting a
programm (see gdb output).
The changes are:
kernel 2.2 -> 2.4
Tcl 8.0 -> 8.4 (maybe here's the problem)
gcc 2.95.2 -> 2.95.3
gdb output --->
Starting program:
/home/rd1/m18s3/daten/test/swarmapps-2.1.1/heatbugs/.libs/heatbugs
Program received signal SIGSEGV, Segmentation fault.
0x1 in __strtol_internal (nptr=0x811fe60 "@\022\013\bè3\013\b",
endptr=0x200000b, base=1, group=1076293910) at eval.c:35
35 eval.c: No such file or directory.
(gdb) bt
#0 0x1 in __strtol_internal (nptr=0x811fe60 "@\022\013\bè3\013\b",
endptr=0x200000b, base=1, group=1076293910) at eval.c:35
#1 0x4026f343 in CreateBusy () at eval.c:88
#2 0x4026f425 in HoldBusy () at eval.c:88
#3 0x4026f5a4 in HoldOp () at eval.c:88
#4 0x4026fad5 in BusyCmd () at eval.c:88
#5 0x403ba617 in TclInvokeStringCommand () at eval.c:88
#6 0x403edfa1 in TclGetOriginalCommand () at eval.c:88
#7 0x403d54e9 in TclExecuteByteCode () at eval.c:88
#8 0x403bb05f in Tcl_EvalObjEx () at eval.c:88
#9 0x403c0c11 in Tcl_ForeachObjCmd () at eval.c:88
#10 0x403f2378 in TclExpandTokenArray () at eval.c:88
#11 0x403f2a8a in Tcl_EvalEx () at eval.c:88
#12 0x403f2d69 in Tcl_Eval () at eval.c:88
#13 0x4012e421 in _i_TclInterp__eval_ (self=0x80922a0, _cmd=0x40128738,
fmt=0x401185c0 "foreach w [winfo children .] {busy hold $w} ;update")
at TclInterp.m:345
#14 0x40104f9d in tkobjc_updateIdleTasks (hold=1) at common.m:260
<--- gdb output
Thanks for advices
Andreas Wegerich
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.
- segmentation fault maybe from Tcl,
Andreas Wegerich <=