Author Topic: "Path not found" when using debugger  (Read 4752 times)

GeoffreyF67

  • Community Member
  • Posts: 6
  • Hero Points: 0
"Path not found" when using debugger
« on: April 17, 2010, 03:03:10 AM »
I'm getting closer!

I have the debugger setup and I can actually launch it and it communicates back with slickedit.

Unfortunately, at that point I get the error "Path not found" in the bottom left hand corner of slickedit as seen in this picture:

http://cl.ly/SWA

I don't know if slickedit is complaining that it can't find a file on my local system or if it's xdebug that is complaining that it can't find a file on the server.

I've put this into my php file in the hopes it would fix the problem (it did not):

ini_set('include_path',ini_get('include_path') . ':/home/dst/www/dst2');

Any help would be greatly appreciated!

G-Man

Rodney

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 798
  • Hero Points: 54
Re: "Path not found" when using debugger
« Reply #1 on: April 17, 2010, 04:05:11 AM »
Yes, as you guessed, the debugger is probably passing us a remote path that we have no clue how to map. This happens when debugging a remote target/web server. Typically this would have been set up correctly when creating the project through the wizard. Try setting up a local <=> remote mapping from Build>PHP Options, Run tab, File mapping.

If you cannot figure out which remote path is the problem, you can:
* turn on debug logging by setting def_debug_logging=1 on the SE command line
* run the debugger through the point you get the error
* stop debugging
* inspect 'vs.log' in your config-directory (Help>About)
* look for lines with "warning: unable to map remote file..." which indicate stopping at a breakpoint and not being able to map back to a local file
* look for lines with "warning: unable to map local file..." which indicate not being able to set a breakpoint on the remote side

Keep in mind that if all your debugging is taking place locally, then those warnings are meaningless (which is why they are warnings and not errors).

Also, do not forget to set def_debug_logging=0 when you are done.

--rodney
« Last Edit: April 17, 2010, 04:13:12 AM by Rodney »

GeoffreyF67

  • Community Member
  • Posts: 6
  • Hero Points: 0
Re: "Path not found" when using debugger
« Reply #2 on: April 17, 2010, 03:07:35 PM »
Thanks!

After lots of mucking with it, I did figure out the problem...

/home/dst/www/dst2 - folder I was using

/home/dst/public_html/dst2 - folder that worked

LOL - www maps to the public_html folder so it *should* have worked.

Go figure.

G-Man

Rodney

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 798
  • Hero Points: 54
Re: "Path not found" when using debugger
« Reply #3 on: April 17, 2010, 04:33:36 PM »
The Xdebug plugin on the server always resolves symbolic links in my experience. Glad you figured it out.

--rodney