Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General Discussion » View Thread |
Messages 1 to 3 of 3 total |
How to use XP and D5 Debugging |
Sat, Apr 12 2008 2:02 PM | Permanent Link |
"Jerry Clancy" | As noted in the earlier thread, Engine Error # 11010, I ran into what turned
out to be an unexpected but apparently common problem, D5 not seeing breakpoints and symbols in the IDE when debugging under XP. It turns out that there were numerous posts, many going back years, offering advice on how to overcome this, much of which didn't work. However, I finally did run into one piece by Jetzt Bewerten written about a year ago that offered three alternatives of which I found only one really workable in an on-going sense, so I offer it here should another elevate user run into this situation. The problem, essentially, is due to changes that MS made with XP it broke D5 in debegging because it could no longer find its symbol table. I use Omnicron's OmniHttpd as a development test server so the comments below are in that context but they should work with any server.\ .. Setup (ie, just leave it as is) the server as normal. By default Omni would put the server .exe in drive:\httpd and the ISAPI folder would be drive:\httpd\isapi. .. Put your .pas, .dfm files in a project directory as you normally would. .. However, in a departure from normal development which would also put the project-related files (.dpr, .dof, .cfg, .res) in the development directory, put them instead into the ISAPI (or script) directory. The easiest way to do this is to simply do a Save Project As into the appropriate directory. .. Set the Project | Options | Directories Output to the ISAPI/Script directory (or just leave it blank with the project save there) and the Units Ouput set to your project directory (typically). .. Set Run | Parameters | Local Host Application to the location of the server itself, in Omni's case to "Drive:\httpd\OHTTPD.exe". Also, make sure that Remote debugging is off. That should do it. Basically, the only thing you are doing differently is saving the projects to the application (ISAPI/Scripts) folder, which is a bit weird but OK on the development system and it beats having to run out and spend $400 or more just because the debugger doesn't work anymore. I just don't want the next guy to go through two days of hell likd I did sorting this out when I moved to XP from Win2K. Jerry |
Mon, Apr 14 2008 1:18 PM | Permanent Link |
Lance Rasmussen Jazzie Software Team Elevate | Thanks for posting this.
Lance "Jerry Clancy" <jclancy@billtrak.com> wrote in message news:60A6E04E-1709-4788-8AE8-68C38A0640AE@news.elevatesoft.com... > As noted in the earlier thread, Engine Error # 11010, I ran into what > turned out to be an unexpected but apparently common problem, D5 not > seeing breakpoints and symbols in the IDE when debugging under XP. It > turns out that there were numerous posts, many going back years, offering > advice on how to overcome this, much of which didn't work. However, I > finally did run into one piece by Jetzt Bewerten written about a year ago > that offered three alternatives of which I found only one really workable > in an on-going sense, so I offer it here should another elevate user run > into this situation. > > The problem, essentially, is due to changes that MS made with XP it broke > D5 in debegging because it could no longer find its symbol table. I use > Omnicron's OmniHttpd as a development test server so the comments below > are in that context but they should work with any server.\ > > . Setup (ie, just leave it as is) the server as normal. By default Omni > would put the server .exe in drive:\httpd and the ISAPI folder would be > drive:\httpd\isapi. > > . Put your .pas, .dfm files in a project directory as you normally would. > > . However, in a departure from normal development which would also put the > project-related files (.dpr, .dof, .cfg, .res) in the development > directory, put them instead into the ISAPI (or script) directory. The > easiest way to do this is to simply do a Save Project As into the > appropriate directory. > > . Set the Project | Options | Directories Output to the ISAPI/Script > directory (or just leave it blank with the project save there) and the > Units Ouput set to your project directory (typically). > > . Set Run | Parameters | Local Host Application to the location of the > server itself, in Omni's case to "Drive:\httpd\OHTTPD.exe". Also, make > sure that Remote debugging is off. > > That should do it. Basically, the only thing you are doing differently is > saving the projects to the application (ISAPI/Scripts) folder, which is a > bit weird but OK on the development system and it beats having to run out > and spend $400 or more just because the debugger doesn't work anymore. > > I just don't want the next guy to go through two days of hell likd I did > sorting this out when I moved to XP from Win2K. > > Jerry > > |
Tue, Apr 15 2008 1:15 PM | Permanent Link |
"Jerry Clancy" | You're welcome.
Jerry "Lance Rasmussen [Team Elevate]" <lance@jazziesoftware.com> wrote in message news:F4803EC0-57A4-4E0F-A9E7-2B82A6E0C8DE@news.elevatesoft.com... > Thanks for posting this. > > Lance |
This web page was last updated on Friday, March 29, 2024 at 03:30 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |