Description: |
Version: Tcl/Tk Aqua 8.4.1
OS: OS X 10.2 (Jaguar)
Extensions: Itcl/Itk/Iwidgets supplied with Aqua version
Many of my dialog boxes that were created using
iwidgets dialogshell and contain other iwidgets crash
sometime during the activation process (e.g., "$ds
activate" where $ds is the variable assigned the dialog
box widget). The dialog box itself appears, but it seems
to crash during the drawing of its component widgets.
There is no core dump file, the application just closes
inexplicably. It occurs on virtually all such dialog boxes
in the scripts that I have tried. I have tried setting the
dialog boxes to be both modal and modeless, with no
change in behavior.
The file in which this occurs is quite large, but it is from
another SourceForge-hosted project OpenSoundWorld, I
am happy to send to whomever is handling this request.
I have tried unsuccessfully to isolate the problem using
puts statements and strategic "commenting out" of
lines to no avail.
Since it appears to happen in Tcl scripts and I can't
isolate it to a particular Tk issue, I'll try here first. If
someone knows this to be a Tk issue, I'll happily refer it
on to that project.
Any help would be appreciated! Thanks!
-Amar
[email protected]
|
User Comments: |
wolfsuit added on 2004-07-30 07:11:11:
Logged In: YES
user_id=169107
First of all, can you try this with a more recent version of Tcl/Tk? 8.4.1
is pretty old now, and was only the second AquaTk release. Lots of
bugs have been fixed since then.
Second, Mac OS X doesn't make core files by default. Instead, a record
of the crash will be written to ~/Library/Logs/CrashReporter/Wish
Shell.app.crash.log. Can you look to see if a crash log was written
there? Note that this is a cumulative log, so if that file exists, you have
to look & make sure there is an entry from the time of the crash.
If there is, please add the information from that log to the bug.
If there isn't, then you are getting some kind of a Tcl error that is
causing the app to exit, and not a crash. One way to figure out what is
going on there is to wrap the suspect code in a "catch" statement, and
then printing out $errorInfo if catch returns an error.
|