Re: Problems with Workbench Debugger Breakpoints
- To: mathgroup at smc.vnet.net
- Subject: [mg111099] Re: Problems with Workbench Debugger Breakpoints
- From: Nate Dudenhoeffer <ndudenhoeffer at gmail.com>
- Date: Tue, 20 Jul 2010 03:43:52 -0400 (EDT)
Thanks for the suggestion David, I was not aware of that. However, in this case all of the packages are in the same project. I have gotten the debugger to work sporadically, and managed to debug the code using a series of pauses and dialog boxes, but I would still like to determine the root cause of my problem. Nate On Mon, Jul 19, 2010 at 6:46 AM, David Park <djmpark at comcast.net> wrote: > I haven't actually used the debugger or done this myself, so I may be on > shaky ground. > > But I believe it you want to debug across multiple applications, that is > multiple application projects in Workbench and not simply multiple packages > within one application project, then you have to specify references to > other > projects. > > Right click on the project and go to "Properties" (at the bottom) on the > context menu. Select "Project References" and check the other applications > that are involved in the debugging. > > > David Park > djmpark at comcast.net > http://home.comcast.net/~djmpark/ <http://home.comcast.net/%7Edjmpark/> > > > From: Nate Dudenhoeffer [mailto:ndudenhoeffer at gmail.com] > > > I have several packages for which the breakpoints do not seem to work in > the > Wolfram Workbench debugger. When I copy the content to a new package it > works as expected. I don't have a lot of experience using the debugger, > but > I have played with it on and off for a few months, and haven't seen this > issue before. > > Is there some setting that I have missed? Or are my packages somehow > getting corrupted? It doesn't seem like there's a whole lot in the forum > about Workbench, has anyone else seen similar issues? > > I think I have traced the issue to a package that has some of my basic > functions in it. I am debugging some code in an upper level package with > calls three other packages. One of the three is also called within each of > the other two, and I believe the issue is in this one. The private > functions within that package don't seem to work unless it is called > explicitly by at the top level. I am still learning how some of the > relationships work between packages, so please feel free to shed some light > here if you would like. > > > Thanks in advance, > Nate > > --00163630ef0bf761ed048bc653ae Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Sun-Content-Length: 2881 Thanks for the suggestion David, I was not aware of that. However, in th= is case all of the packages are in the same project. <br><br>I have gott= en the debugger to work sporadically, and managed to debug the code using a= series of pauses and dialog boxes, but I would still like to determine the= root cause of my problem.<br> <br>Nate<br><br><div class="gmail_quote">On Mon, Jul 19, 2010 at 6:46 AM,= David Park <span dir="ltr"><<a href="mailto:djmpark at comcast.net">dj= mpark at comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote= " style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, = 204); padding-left: 1ex;"> I haven't actually used the debugger or done this myself, so I may be o= n<br> shaky ground.<br> <br> But I believe it you want to debug across multiple applications, that is<br= > multiple application projects in Workbench and not simply multiple packages= <br> within one application project, then you have to specify references to othe= r<br> projects.<br> <br> Right click on the project and go to "Properties" (at the bottom)= on the<br> context menu. Select "Project References" and check the other app= lications<br> that are involved in the debugging.<br> <br> <br> David Park<br> <a href="mailto:djmpark at comcast.net">djmpark at comcast.net</a><br> <a href="http://home.comcast.net/%7Edjmpark/"; target="_blank">http://ho= me.comcast.net/~djmpark/</a><br> <br> <br> From: Nate Dudenhoeffer [mailto:<a href="mailto:ndudenhoeffer at gmail.com">= ndudenhoeffer at gmail.com</a>]<br> <div><div></div><div class="h5"><br> <br> I have several packages for which the breakpoints do not seem to work in th= e<br> Wolfram Workbench debugger. When I copy the content to a new package it<= br> works as expected. I don't have a lot of experience using the debugg= er, but<br> I have played with it on and off for a few months, and haven't seen thi= s<br> issue before.<br> <br> Is there some setting that I have missed? Or are my packages somehow<br> getting corrupted? It doesn't seem like there's a whole lot in t= he forum<br> about Workbench, has anyone else seen similar issues?<br> <br> I think I have traced the issue to a package that has some of my basic<br> functions in it. I am debugging some code in an upper level package with= <br> calls three other packages. One of the three is also called within each = of<br> the other two, and I believe the issue is in this one. The private<br> functions within that package don't seem to work unless it is called<br= > explicitly by at the top level. I am still learning how some of the<br> relationships work between packages, so please feel free to shed some light= <br> here if you would like.<br> <br> <br> Thanks in advance,<br> Nate<br> <br> </div></div></blockquote></div><br> --00163630ef0bf761ed048bc653ae--