[Date Index] [Thread Index] [Author Index]

Re: Problems with Workbench Debugger Breakpoints

• To: mathgroup at smc.vnet.net
• Subject: [mg111067] Re: Problems with Workbench Debugger Breakpoints
• From: Nate Dudenhoeffer <ndudenhoeffer at gmail.com>
• Date: Mon, 19 Jul 2010 02:09:16 -0400 (EDT)
• References: <AANLkTin36gQZhJ2UI9QTLZjoRNk_O3AX4N8BB8AJXDQT@mail.gmail.com>

Here are a few more details and a corrections to my original post:

Here is the structure: level3.m calls in the package definition level1.m,
level2_1.m and level2_2.m.  Both of the level2 packages also call level1.

My statement about private functions not working was incorrect.  What I
should have said is that although level2 calls level1, to use level1 within
level3 it seems I need to call it explicitly.

Debugging seems to work fine in both of the level two packages, but not
level1 or level3.

I also stated that I copied the contents to a new package and that solved
the problem, that was only temporary.  After running the debugger a few
times, I ran into the same issue again.  Maybe it's just a settings issue
that I am missing?

Nate


On Sun, Jul 18, 2010 at 10:22 AM, Nate Dudenhoeffer <ndudenhoeffer at gmail.com
> wrote:

> 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
>