DEBUG crashes on startup

Discussions specific to Team Developer 5.2.

DEBUG crashes on startup

Postby alan.cousins » Wed Aug 26, 2015 4:44 pm

I am looking for Help with getting DEBUG working as I need to be more productive
I am using TD 5.2 sp3. Tried going to sp5 but it introduced bugs that could not be resolved in time for a release of software.
Similarly going to TD 6 is not an option as the rewrite time is prohibitive for a very small team supporting a range of products.
I have been unable to use the debug function for quite some time.
I have reinstalled TD a number of times Including on a new machine. However none of my attempts have been able to resolve the problem.
TD crashes almost immediately after pressing the 'Start Execution' button
It does the compile then tries to start. The first line in our AppStartup (Called from On SAM_AppStartup)
calls our Login apd to get login details it crashes as soon as this is called. However if running the compiled exe the application processes this command fine.
All of our applications use this logon.
I have noticed however if I have a fairly small application the debug will work. However as most of our Applications have been developed over 15 years they are not small.
Any suggestions would be appreciated.

This is listed in the Event Log
Faulting application name: cbi52.exe, version: 5.2.3.24308, time stamp: 0x4d74ab02
Faulting module name: cdlli52.dll, version: 5.2.3.24308, time stamp: 0x4d74ad9a
Exception code: 0xc0000005
Fault offset: 0x000eecf0
Faulting process id: 0x25d0
Faulting application start time: 0x01d0e054fee4be95
Faulting application path: C:\Program Files (x86)\Unify\Team Developer 5.2\cbi52.exe
Faulting module path: C:\Program Files (x86)\Unify\Team Developer 5.2\cdlli52.dll
Report Id: aa3037e6-4c49-11e5-bf1b-94de807763b7
Faulting package full name:
Faulting package-relative application ID:

Thanks
Alan
alan.cousins
 
Posts: 1
Joined: Wed Aug 26, 2015 2:19 am

Re: DEBUG crashes on startup

Postby Dave Rabelink » Wed Aug 26, 2015 11:20 pm

What happens when you use a small login apd doing stuff hardcoded and returning fixed data?
How does the login apd expose it's interface?
(using exported forms/functions/global vars?)

Ever tried to include the source of the login apd into the main application (so do not use apd but the source instead) ?

Have you checked this list of known dynalib issues:
http://tdwiki.daverabelink.net/index.ph ... orkarounds
Regards,
Dave Rabelink

Image
Articles on Team Developer Wiki
Download samples from TD Sample Vault

Image
Go forward! Come join the TD, SqlBase & TDMobile community on
Team Developer Community Forum
User avatar
Dave Rabelink
 
Posts: 1655
Joined: Sat Feb 17, 2007 12:01 am
Location: Gouda, The Netherlands


Return to Team Developer 5.2

Who is online

Users browsing this forum: No registered users and 2 guests