Re: Debugging frameworks

From: Hordur Thordarson (hordu..ausn.is)
Date: Thu Sep 15 2005 - 16:23:38 EDT

  • Next message: Hordur Thordarson: "Re: Debugging frameworks - [Possible SPAM] Bayesian Filter detected spam"

    Yes, seeing as there's a debugger there, I figured I'd use that rather
    than trusty, old System.out.println() or alternatives :-)

    Hörður Þ.
    Lausn hugbúnaður ehf
    Tel. +354-534-5005 / +354-699-1068
    Web: http://www.lausn.is

    On 15.9.2005, at 19:47, Watkins, Garry wrote:

    > Probably it is easier to step through the code with the integrated
    > debugger in eclipse. ;)
    >
    > -----Original Message-----
    > From: Kieran Kelleher [mailto:kieran_list..ac.com]
    > Sent: Thursday, September 15, 2005 3:44 PM
    > To: woproject-de..bjectstyle.org
    > Subject: Re: Debugging frameworks
    >
    > Have you tried logging as an alternative?
    >
    > On Sep 15, 2005, at 2:03 PM, Hordur Thordarson wrote:
    >
    >> Hi all,
    >>
    >> What is the magic step I'm missing in order to be able to debug my WO
    >> framework while running my WO app in Eclipse ?
    >>
    >> I've got a simple app that uses 3 frameworks. One of these I'd like
    >> to be able to put breakpoints in and step through. I have this
    >> framework referenced as a workspace project in my app whereas the
    >> other two frameworks are just referenced in /Library/Frameworks as
    >> usual.
    >>
    >> My app works fine and the framework's functionality is there and all,
    >> but my framework breakpoints don't trigger :-(
    >>
    >>
    >>
    >> Hörður Þ.
    >> Lausn hugbúnaður ehf
    >> Tel. +354-534-5005 / +354-699-1068
    >> Web: http://www.lausn.is
    >>
    >
    >
    >
    >
    >
    >
    > Confidential & Privileged
    >
    > Unless otherwise indicated or obvious from its nature, the information
    > contained in this communication is attorney-client privileged and
    > confidential information/work product. This communication is intended
    > for the use of the individual or entity named above. If the reader of
    > this communication is not the intended recipient, you are hereby
    > notified that any dissemination, distribution or copying of this
    > communication is strictly prohibited. If you have received this
    > communication in error or are not sure whether it is privileged,
    > please immediately notify us by return e-mail and destroy any
    > copies--electronic, paper or otherwise--which you may have of this
    > communication.
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Thu Sep 15 2005 - 16:23:40 EDT