I’m not on a Mac, but having helped people with solving problems with step debugging CFML for years (whatever their platform), I’ll see if I can help here.
It may help, though, to clarify more about your setup in both CFE and your CFML server.
Since you’re asking on the cfeclipse group, I’ll assume you’re not using CF Builder. So did you set that up using the old CF8 “eclipse extensions for CF”, which offered the debugger before it was built-into CFB (and was never updated after that)? Or might you be using FusionDebug, the commercial alternative for step debugging (which does support CFE, CFB, and indeed any Eclipse platform, whether for CF or Railo or Lucee)?
Especially with respect to suggesting specific places to look for settings in the debug config within Eclipse, it could help for us to know which you are using (and which CFML server).
For instance, as for your saying your new setup could not debug anything but your root, just to be clear, are you saying you have no problem running the pages (in tyour browser)? I ask because there can be problems with the web server connector (especially in CF10 and 11) where you may find that it can’t run anything under the root. You only say that when you step debug into a subdir the debugger “can’t find it”. Are you saying it really is only the debugger? You have no problem browsing to CFML templates in such a subdir?
Then you say things are configured identically. Are you saying you went to the debugger configuration settings and added any mappings, which may have been required on the old setup? Again, without knowing the exact CFML debugger you’re using I hesitate to point to a specific tab/setting name, but it’s in the edit of the debug config in all of them.
Finally, you don’t clarify: is your CFML server on the same machine as CFE? If so, you generally shouldn’t need to bother with any sort of mapping (but there are cases where you must). Since you say it “can’t find the source”, it would help to know for sure.
Hope that’s helpful.
/charlie
I’m not on a Mac, but having helped people with solving problems with step debugging CFML for years (whatever their platform), I’ll see if I can help here.
It may help, though, to clarify more about your setup in both CFE and your CFML server.
Since you’re asking on the cfeclipse group, I’ll assume you’re not using CF Builder. So did you set that up using the old CF8 “eclipse extensions for CF”, which offered the debugger before it was built-into CFB (and was never updated after that)? Or might you be using FusionDebug, the commercial alternative for step debugging (which does support CFE, CFB, and indeed any Eclipse platform, whether for CF or Railo or Lucee)?
Especially with respect to suggesting specific places to look for settings in the debug config within Eclipse, it could help for us to know which you are using (and which CFML server).
For instance, as for your saying your new setup could not debug anything but your root, just to be clear, are you saying you have no problem running the pages (in tyour browser)? I ask because there can be problems with the web server connector (especially in CF10 and 11) where you may find that it can’t run anything under the root. You only say that when you step debug into a subdir the debugger “can’t find it”. Are you saying it really is only the debugger? You have no problem browsing to CFML templates in such a subdir?
Then you say things are configured identically. Are you saying you went to the debugger configuration settings and added any mappings, which may have been required on the old setup? Again, without knowing the exact CFML debugger you’re using I hesitate to point to a specific tab/setting name, but it’s in the edit of the debug config in all of them.
Finally, you don’t clarify: is your CFML server on the same machine as CFE? If so, you generally shouldn’t need to bother with any sort of mapping (but there are cases where you must). Since you say it “can’t find the source”, it would help to know for sure.
OK, thanks for that.
So when you say, “Mappings in the eclipse debugger are identical as far as i can tell”, you do mean (I suppose) that you have changed them to be unique to your Mac environment as distinct from the old one, right? For those who may be following along, the mappings for the debugger setup map what the path looks like locally to what they look like on the remote server.
And since you’re on a Mac, have you made sure there are no problems with case sensitivity of those mappings, especially with respect to the local-side mapping?
And when you refer to the settings, are these ones you’re making in the Preferences area, or the specific “Debug configuration” you will have created (under the Run menu)?
Also, to be clear, you have to open the file in Eclipse from within a project (using the Navigator). You are doing that, right? Not just opening the file using the File Explorer?
One more thing: in CF, at least, and with respect to its debugger, Adobe has documented a useful jvm argumente:
-DDEBUGGER_TRACE=true
which causes CF to log extra info (to the console or the ColdFusion-out.log), which can be useful to understand the interaction between the debugging client and the server (including success of your mappings). I don’t know if that’s only useful if using the debugger as they have implemented it in CFBuilder, but it’s worth a shot if none of the other ideas I’ve shared help (and no one else proposes a better solution for you).
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Monday, December 14, 2015 2:22 PM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
inline responses below
<snip>
OK, thanks for that.
So when you say, “Mappings in the eclipse debugger are identical as far as i can tell”, you do mean (I suppose) that you have changed them to be unique to your Mac environment as distinct from the old one, right? For those who may be following along, the mappings for the debugger setup map what the path looks like locally to what they look like on the remote server.
And since you’re on a Mac, have you made sure there are no problems with case sensitivity of those mappings, especially with respect to the local-side mapping?
And when you refer to the settings, are these ones you’re making in the Preferences area, or the specific “Debug configuration” you will have created (under the Run menu)?
Also, to be clear, you have to open the file in Eclipse from within a project (using the Navigator). You are doing that, right? Not just opening the file using the File Explorer?
One more thing: in CF, at least, and with respect to its debugger, Adobe has documented a useful jvm argumente:
-DDEBUGGER_TRACE=true
which causes CF to log extra info (to the console or the ColdFusion-out.log), which can be useful to understand the interaction between the debugging client and the server (including success of your mappings). I don’t know if that’s only useful if using the debugger as they have implemented it in CFBuilder, but it’s worth a shot if none of the other ideas I’ve shared help (and no one else proposes a better solution for you).
Did you try that trace option?
BTW, note that you can also do debugging in the new FR6, whereby you do the debugging not with any IDE but via FR’s web interface. It’s a powerful new capability (And designed even to be safe for production, with many protections that keep it ill-effecting the server being monitored, or in this case debugged). As for pricing concerns, I’ll note in advance that it’s only in the new “ultimate” edition of FR, but is indeed in the free trial which one can try for 14 days.
Still, I’d love to hear if that trace flag may have helped you, with the old eclipse-CF-extensions approach you are using.
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Wednesday, December 16, 2015 11:14 AM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
Guess i give up and go back to eclipse on windows. the only thing that works. I'd pay $200 for fusiondebug at this point, but not $200 a YEAR. just want to buy my tools and get to work.
I'd give my left nut for a real development environment, but i'm not holding my breath, Adobe. Microsoft's ASP.NET MVC is starting to look real good.
On Tuesday, December 15, 2015 at 7:12:29 AM UTC-5, funaroma wrote:
once again inline...
<snip>
BTW, about pricing and the hope of a “real dev environment for CF”, do note that IntelliJ IDEA is $500 per year to start. As always, we generally get what we pay for. :-)
/charlie
From: Charlie Arehart [mailto:charli...@carehart.org]
Sent: Wednesday, December 16, 2015 2:08 PM
To: 'cfeclip...@googlegroups.com'
Subject: RE: [cfeclipse-users] debugger frustrations
Did you try that trace option?
BTW, note that you can also do debugging in the new FR6, whereby you do the debugging not with any IDE but via FR’s web interface. It’s a powerful new capability (And designed even to be safe for production, with many protections that keep it ill-effecting the server being monitored, or in this case debugged). As for pricing concerns, I’ll note in advance that it’s only in the new “ultimate” edition of FR, but is indeed in the free trial which one can try for 14 days.
Still, I’d love to hear if that trace flag may have helped you, with the old eclipse-CF-extensions approach you are using.
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Wednesday, December 16, 2015 11:14 AM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
Guess i give up and go back to eclipse on windows. the only thing that works. I'd pay $200 for fusiondebug at this point, but not $200 a YEAR. just want to buy my tools and get to work.
I'd give my left nut for a real development environment, but i'm not holding my breath, Adobe. Microsoft's ASP.NET MVC is starting to look real good.
On Tuesday, December 15, 2015 at 7:12:29 AM UTC-5, funaroma wrote:
once again inline...
<snip>
Fair enough. And to be clear, you were trying to work with the Eclipse Extensions for CF which were from CF8. They should work, but they are indeed quite old.
You say you are changing to CF10, but that may not help things. You’re still using the old “client”. BTW, you may also want to consider CFBuilder, which has the newer Adobe-provided debugger capability built-in.
I know this is a CFE group, so mentioning CFB is borderline heretical, but I’m just saying that the only formally supported CFML debugger for Eclipse (and CF Eclipse) is FD, so if you don’t want to use that, and can’t get the old Adobe extensions-based approach to work, then CFB is at least an alternative to consider, even if only for debugging. And note that you get a free trial (60 days, I think), after which it reverts to a free edition, and from my testing the step debugging does still work in that free edition.
All that said, I don’t see how the trace option would have led to “more frustration” of the sort you mention. It should not prevent the debugger starting, or affect what can be debugged. Are you really saying those problems arose after you put in that option and restarted CF? BTW, what version of CF are you talking to? The trace option (if it works) should instead HELP you solve the problem by showing what the debugger (on the server) receives as a request from the IDE (as the client). It really should help solve the problems you were describing before, not add to them. :-)
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Wednesday, December 16, 2015 2:36 PM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
I started down the path of trying the trace option, only to meet more frustration -- I'm having trouble simply getting the debugger to start when i set a breakpoint and load a page in the eclipse browser. sometimes it works, sometimes it doesn't. when it does, eclipse on mac cannot find the files on the windows server, even though eclipse on my windows 7 instance handily finds them on the same server, with the same configuration.
Fair enough. And to be clear, you were trying to work with the Eclipse Extensions for CF which were from CF8. They should work, but they are indeed quite old.
You say you are changing to CF10, but that may not help things. You’re still using the old “client”. BTW, you may also want to consider CFBuilder, which has the newer Adobe-provided debugger capability built-in.
I know this is a CFE group, so mentioning CFB is borderline heretical, but I’m just saying that the only formally supported CFML debugger for Eclipse (and CF Eclipse) is FD, so if you don’t want to use that, and can’t get the old Adobe extensions-based approach to work, then CFB is at least an alternative to consider, even if only for debugging. And note that you get a free trial (60 days, I think), after which it reverts to a free edition, and from my testing the step debugging does still work in that free edition.
All that said, I don’t see how the trace option would have led to “more frustration” of the sort you mention. It should not prevent the debugger starting, or affect what can be debugged. Are you really saying those problems arose after you put in that option and restarted CF? BTW, what version of CF are you talking to? The trace option (if it works) should instead HELP you solve the problem by showing what the debugger (on the server) receives as a request from the IDE (as the client). It really should help solve the problems you were describing before, not add to them. :-)
You say you appreciate my persistence, and I thank you for that, but then is your first in-line reply said in jest? Of course MARS is not old, but the Eclipse extensions for CF really are. They were released with CF8 in 2007, and have not been updated since. That’s what I was referring to. (I had no info on the Eclipse version you were using, and it wouldn’t have mattered with respect to this point.)
And as for your observation about not finding a free edition, well, you seem to have misread my words. I was referring to CFBuilder (also as “CFB”), which after 60 days reverts to a free edition. I should note as well that CFB is offered either as a standalone edition (Eclipse installed and branded as CFB), as well as a plug-in edition (which you can add to an existing Eclipse setup).
My point was simply that if perhaps the old Eclipse extensions for CF were a factor in your challenge, there are these other alternatives.
Since no one else here is interjecting on the challenge, we just won’t know if what you wanted to do originally (from Mac) could work. It may, or perhaps your new approach may.
Finally, not sure why you’re wanting to do port forwarding. You don’t need to use CF with its port 8500. That’s what you get if you tell it to not use an external web server. If you do have Apache or IIS, you can tell CF to use that, and then use port 80 to get to your CFML pages.
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Wednesday, December 16, 2015 3:27 PM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
I appreciate your persistence.
Answers below
On Wednesday, December 16, 2015 at 3:58:55 PM UTC-5, charlie arehart wrote:
Thanks for the clarification. Hope you can get things sorted out.
/charlie
From: cfeclip...@googlegroups.com [mailto:cfeclip...@googlegroups.com] On Behalf Of funaroma
Sent: Wednesday, December 16, 2015 6:54 PM
To: CFEclipse Users
Subject: Re: [cfeclipse-users] debugger frustrations
no no no. i only meant that i knew the CF Extensions were. I was simply agreeing with you. =D
I must be exhaused... writing things wrong and reading things wrong too. I'll have to check and see what the free version of CFBuilder can do, indeed. I hate to be a
<snip>