Skip to main content

Question for the VFP team: Why can't the debugger get the code?

There are many reasons why the debugger can't always get the code but as a developer, one always wants to ask.
 
I have several apps. I turn on "Include Debugger code" in the project manager. When an error occurs, why can't the debugger find the information?
 
Yes. The debugger can read the Class code and shows it. but PRG files (where many developers keep their code) are kept hidden from this area.
 
There may be ways around it but WHY can't VFP read the "include debugging" code from program files?
 

Comments

Anonymous said…
Do you have sample code to reproduce your scenario?
Are you running an EXE? Are you DOing an APP or EXE from the command window?
Repro code shows unambiguously what you mean.
March 23, 2005 at 11:57 PM
Andrew MacNeill said…
Typically this happens when you have your source in one directory where you build your project and then you are running it in another directory and then trying to debug it.

Simplest steps to reproduce:

Build a project:
MAIN.PRG
DO FORM X

Function WhatsmyName
IF SYS(0)="andrew"
RETURN "Good"
ELSE

RETURN "Bad"
ENDIF

The form has a button on it that does
MESSAGEBOX(WhatsMyName())

Now build this as an EXE or an APP.

If you run it in your Dev environment and use the debugger, you can see all of the code.

Copy the app to another folder, restart VFP and then try again using the debugger with a Breakpoint on PROGRAM(). The code in the BUTTON click will show but the code in MAIN.PRG will be "Source Not Available"

Make sense?
March 24, 2005 at 7:01 AM
Anonymous said…
Thanks so very much for taking your time to create your blog. Excellent work
November 23, 2005 at 9:05 AM
Post a Comment

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .
4 comments
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...
11 comments
Read more

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...
Post a Comment
Read more