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.
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?
Thanks so very much for taking your time to create your blog. Excellent work

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…