Hi all..
I'd like to know if there's a way to find out if any breakpoints are set anywhere within the image so that I can ensure nothing will be accidentally triggering the debugger if some code is executed for an off-nominal path,etc for a quasi-release image.. Thanks! -- Rick _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
>From the Launcher, open the Debug menu and select Browse Probes. If I
needed to do this programmatically, I'd track down the code behind the menu item and adapt it as needed. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Richard E. Flower Sent: Monday, January 26, 2009 10:02 PM To: VW NC Subject: [vwnc] Any way to find out what breakpoints are set? Hi all.. I'd like to know if there's a way to find out if any breakpoints are set anywhere within the image so that I can ensure nothing will be accidentally triggering the debugger if some code is executed for an off-nominal path,etc for a quasi-release image.. Thanks! -- Rick _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Rick Flower
You can disable probes or remove all of them for deployment. Also, if you build using a clean image to load your code this won't be needed at all.
-Boris (via BlackBerry) ----- Original Message ----- From: [hidden email] <[hidden email]> To: VW NC <[hidden email]> Sent: Mon Jan 26 22:01:44 2009 Subject: [vwnc] Any way to find out what breakpoints are set? Hi all.. I'd like to know if there's a way to find out if any breakpoints are set anywhere within the image so that I can ensure nothing will be accidentally triggering the debugger if some code is executed for an off-nominal path,etc for a quasi-release image.. Thanks! -- Rick _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc winmail.dat (3K) Download Attachment |
In reply to this post by Andres Valloud-6
Thanks Adres! Worked like a charm.. I guess I should RTFM! Oh well..
Thanks again! -- Rick On Jan 26, 2009, at 10:10 PM, Valloud, Andres wrote: >> From the Launcher, open the Debug menu and select Browse Probes. >> If I > needed to do this programmatically, I'd track down the code behind the > menu item and adapt it as needed. > > > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On > Behalf Of Richard E. Flower > Sent: Monday, January 26, 2009 10:02 PM > To: VW NC > Subject: [vwnc] Any way to find out what breakpoints are set? > > Hi all.. > > I'd like to know if there's a way to find out if any breakpoints are > set > anywhere within the image so that I can ensure nothing will be > accidentally triggering the debugger if some code is executed for an > off-nominal path,etc for a quasi-release image.. > > Thanks! > > -- Rick > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Rick
There really is a lot of good stuff that probes and the debugger can do. The pdf documentation explains just about all of it. Read it through, you will be surprised at what it can do. Terry =========================================================== Terry Raymond Crafted Smalltalk 80 Lazywood Ln. Tiverton, RI 02878 (401) 624-4517 [hidden email] <http://www.craftedsmalltalk.com> =========================================================== > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On Behalf Of Richard E. Flower > Sent: Tuesday, January 27, 2009 1:43 AM > To: Valloud, Andres > Cc: VWNC > Subject: Re: [vwnc] Any way to find out what breakpoints are set? > > Thanks Adres! Worked like a charm.. I guess I should RTFM! Oh well.. > > Thanks again! > > -- Rick > > On Jan 26, 2009, at 10:10 PM, Valloud, Andres wrote: > > >> From the Launcher, open the Debug menu and select Browse Probes. > >> If I > > needed to do this programmatically, I'd track down the code behind the > > menu item and adapt it as needed. > > > > > > -----Original Message----- > > From: [hidden email] [mailto:[hidden email]] On > > Behalf Of Richard E. Flower > > Sent: Monday, January 26, 2009 10:02 PM > > To: VW NC > > Subject: [vwnc] Any way to find out what breakpoints are set? > > > > Hi all.. > > > > I'd like to know if there's a way to find out if any breakpoints are > > set > > anywhere within the image so that I can ensure nothing will be > > accidentally triggering the debugger if some code is executed for an > > off-nominal path,etc for a quasi-release image.. > > > > Thanks! > > > > -- Rick > > > > _______________________________________________ > > vwnc mailing list > > [hidden email] > > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ > > vwnc mailing list > > [hidden email] > > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hello,
A while ago, I promised to the Squeak list to contact Randy Giffen, the author of 'Visual Syntax' - a visual form of a VisualWorks Smalltalk browser. He replied and I am attaching a part of what he wrote because it might be of interest to this group as well. His code is excellent and very well designed, but worked on an older version of VisualWorks. For use on the current release or in Squeak, some parts would have to be modified, mostly the user interface code. However, much can be reused and the project is worth looking at. Ivan ---------------- >From Randy: ... I still have a copy of it installed on my desktop machine at work if someone would like a demo There are some examples online: http://www.magma.ca/~rgiffen/visualsyntax.html * Master's thesis on an early version the syntax. * The slides from a demonstration at OOPSLA'96. * A small, unpublished report on an experimental comparison of visual verses textual coding. * An implementation of the syntax for VisualWorks 2.5 (with user's guide) A paper describing the visual syntax was presented at TOOLS 23. A Visual Programming Interface for Smalltalk, R Giffen and I Tomek in "Proceedings of Technology of Object-Oriented Languages and Systems, TOOLS 23" Santa Barbara, California, 1997. R Ege, M Singh, B Meyer eds. IEEE Computer Society, pp. 260-269 Note that some of the concepts were used for the "Visual Snippet Editor" which is part of WebSphere Integration Developer (the tooling for WebSphere Process Server) P.R. Giffen, G. Adams, K. McGuire, R. Tsui, H. Hoffman, "Visual Snippet Editor - Success With Less," vlhcc,pp.212-218, Visual Languages and Human-Centric Computing (VL/HCC'06), 2006 http://www2.computer.org/portal/web/csdl/doi/10.1109/VLHCC.2006.56 _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc vsthesis.zip (258K) Download Attachment vsoopsla.zip (34K) Download Attachment vstest97.zip (13K) Download Attachment vst20ug.doc (592K) Download Attachment vst20.zip (247K) Download Attachment |
Free forum by Nabble | Edit this page |