Hi,
When I attempted to start blox I encountered the following: whitebearded1@molly:~/src/smalltalk-2.2d$ gst -qK browser/Run.st Loading package BloxTK Available tests #balloonTest #callbackTest #canvasTest #colorButtonTest #colorDialogTest #dialogTest1 #dialogTest2 #dropdownTest #editTest #eventTest #fileDialogTest #formattingTest #formTest #hContainerTest #iconTest #imageTest #labelTest #listboxTest #menuTest #popupMenuTest #progressTest #textEventsTest #textTest #vContainerTest Loading package Parser Loading package Browser "Global garbage collection... done" /usr/local/share/smalltalk/browser/Run.st:45: Bytecode verification failed: stack underflow /usr/local/share/smalltalk/browser/Run.st:45: Method verification failed for Blox class>>#idle /usr/local/share/smalltalk/browser/Run.st:45: Aborted (ip 52)Blox class>>#dispatchEvents (ip 120)BrowserMain>>#initialize (ip 20)UndefinedObject>>#executeStatements (ip 0)<bottom> Aborted whitebearded1@molly:~/src/smalltalk-2.2d$ gst -qK browser/Run.st /usr/local/share/smalltalk/browser/Run.st:45: Bytecode verification failed: stack underflow /usr/local/share/smalltalk/browser/Run.st:45: Method verification failed for Blox class>>#idle /usr/local/share/smalltalk/browser/Run.st:45: Aborted (ip 52)Blox class>>#dispatchEvents (ip 120)BrowserMain>>#initialize (ip 20)UndefinedObject>>#executeStatements (ip 0)<bottom> Aborted whitebearded1@molly:~/src/smalltalk-2.2d$ To used all of the defaults for ./configure when I built gst Platform: whitebearded1@molly:~/src/smalltalk-2.2d$ uname -a Linux molly 2.6.15-23-386 #1 PREEMPT Tue May 23 13:49:40 UTC 2006 i686 GNU/Linux Brad Watson ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Brad Watson wrote:
> Hi, > > When I attempted to start blox I encountered the following: A typo caused by bad coverage in the test suite. Fixed with the following one-character patch (I committed to arch an additional change that adds a test case). --- orig/kernel/CompildMeth.st +++ mod/kernel/CompildMeth.st @@ -560,7 +560,7 @@ rewriteAsAsyncCCall: func args: argsArra "descr asyncCall. ^self" literals := { descr. #asyncCall }. - bytecodes := #[ 136 1 64 1 67 0 ]. + bytecodes := #[ 136 1 66 1 67 0 ]. newMethod := CompiledMethod literals: literals Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
In reply to this post by Brad Watson
Paolo,
That corrected it. However, when I attempt to exit BloxTK, I get a: MessageNotUnderstood(Exception)>>#signal Should I be using BloxGTK instead ? Is BloxTK effectively depreciated ? Regards, Brad Watson ----- Original Message ---- From: Paolo Bonzini <[hidden email]> To: Brad Watson <[hidden email]> Cc: [hidden email] Sent: Thursday, November 30, 2006 10:37:58 PM Subject: Re: [Help-smalltalk] 2.2d BloxTK Brad Watson wrote: > Hi, > > When I attempted to start blox I encountered the following: A typo caused by bad coverage in the test suite. Fixed with the following one-character patch (I committed to arch an additional change that adds a test case). --- orig/kernel/CompildMeth.st +++ mod/kernel/CompildMeth.st @@ -560,7 +560,7 @@ rewriteAsAsyncCCall: func args: argsArra "descr asyncCall. ^self" literals := { descr. #asyncCall }. - bytecodes := #[ 136 1 64 1 67 0 ]. + bytecodes := #[ 136 1 66 1 67 0 ]. newMethod := CompiledMethod literals: literals Paolo ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
> That corrected it. However, when I attempt to exit BloxTK, I get a: > > MessageNotUnderstood(Exception)>>#signal > > Should I be using BloxGTK instead ? Is BloxTK effectively depreciated ? No, no, it should be fine... Don't you get a longer backtrace than that? Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
>> That corrected it. However, when I attempt to exit BloxTK, I get a: >> >> MessageNotUnderstood(Exception)>>#signal >> >> Should I be using BloxGTK instead ? Is BloxTK effectively depreciated ? > > No, no, it should be fine... Don't you get a longer backtrace than that? I forgot to tell you that I get none. :-) Paolo _______________________________________________ help-smalltalk mailing list [hidden email] http://lists.gnu.org/mailman/listinfo/help-smalltalk |
Free forum by Nabble | Edit this page |