Xotcl September 2003

xotcl@alice.wu.ac.at

6 participants
5 discussions

how to track a segmentation fault problem in Xotcl?
by Catherine Letondal 04 Jan '04

04 Jan '04

Hi, I have just re-installed Xotcl 1.0.2 version and succedeed in running my application with some minor changes since the last xotcl version I used on this platform (Sparc/Solaris 7) was the 0.9 :-) I have a segmentation fault that occurs when a command is called from a Tk menu. The command is attached to the popup by a: add command -command statement on a menu Tk widget that is raised by a tk_popup. However, the very same command, when called from the tcl (xowish) interpreter, works and does not produce any core dump. And most menu items also work well. So my question is: how do I debug such a situation? Thanks for any help... -- Catherine Letondal -- Pasteur Institute Computing Center

3 7

Serializer "bug"
by MichaelL＠frogware.com 17 Sep '03

17 Sep '03

Since you're getting 1.1 ready... I ran across a very, very subtle bug. I was using the serializer to serialize an obj tree. The topological sorting wasn't quite working for one case. In the end, I tracked it down to the fact that I was passing in an unqualified name. The sorting routine was in turn using fully qualified references as it tried to build the correct ordering, and the mismatch meant that it got some orderings for the root object slightly wrong. (Basically a few objects were being created before their containers; their containers were objects aggregated by the root object.) In effect, I was using this: Serializer deepSerialize obj when I should have been using this: Serializer deepSerialize ::obj I don't think you'd be able to reproduce this easily, because it turned out to relate to a specific set of objects and relationships. It turns out that for other reasons, even when you make this "mistake" the algorithm nearly works. To make this work you'd either have to a) require fully qualified names or b) turn a name into a fully qualified name. I don't know enough about Tcl internals to say that (b) is a realistic option--but on the face of it it doesn't seem like it would be. Don't know if this helps much. :-)

2 2

Crash on exit with XOTcl loaded twice
by MichaelL＠frogware.com 16 Sep '03

16 Sep '03

The following script produces a "Tcl_Release couldn't find reference for 0x..." message followed by an "abnormal program termination" when Tcl exits: package require XOTcl set Interp [interp create] $Interp eval {package require XOTcl} interp delete $Interp As you can see, XOTcl is being loaded once in the main interpreter and once in a sub-interpreter. I'm running XOTcl 1.0.2 with Tcl 8.4.2 and 8.4.4 on Windows.

2 3

Re: Approved
by gustaf.neumann＠wu-wien.ac.at 05 Sep '03

05 Sep '03

See the attached file for details

1 0

XOTclIDE Version 0.50
by Artur Trzewik 01 Sep '03

01 Sep '03

Hi! New Version of XOTclIDE 0.50 is released. http://www.xdobry.de/xotclIDE There are new overworked documentation (also in PDF) "XOTclIDE User Guide" with new tutorials. changes: - undo for editor (only for Tcl8.4) - spinbox windows in "Component Browser" - big fixes in code importer (procedures defined in namespace eval can be imported) - changes for better saving and loading components from file system - another small changes see CHANGES file Artur Trzewik <<Havu multa ĝojon de ĝi>>

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Xotcl September 2003