search

trident-job / delphi-code-coverage

Automatically exported from code.google.com/p/delphi-code-coverage
0 stars 0 forks source link

Support packages #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run
2. Configure
3. Run Coverage

What is the expected output? What do you see instead?

In-depth BPL analysis

What version of the product are you using? On what operating system?

RC1

Please provide any additional information below.

Original issue reported on code.google.com by linards....@gmail.com on 22 Mar 2012 at 2:53

GoogleCodeExporter commented 9 years ago 
The startup might be here for support...

http://stackoverflow.com/questions/4205903/bpl-file-needs-run-time-packages

Possible TODO:
 - add seperate list for packages
 - during covering of *.pas, scan for entry point by some kind of mask
 - try to go into package by continuing to set breakpoints ( jopefully dcc32.exe supports this ) ...
 - grab the output as usual of if it is not possible, parse package. What excatly to parse I dunno as I have not so specific knowledge what are compile-time files for bpls or what kind of data manipulations bpl excatly have that makes it non-default-DLL ...

Original comment by linards....@gmail.com on 22 Mar 2012 at 4:43

GoogleCodeExporter commented 9 years ago 
Also interesting tips that mmight come handy ..

http://www.stevetrefethen.com/blog/WhyTheDelphiDebuggerMightFailToStopAtYourBrea
kpoint.aspx

Original comment by linards....@gmail.com on 22 Mar 2012 at 4:49

GoogleCodeExporter commented 9 years ago 
And also this one ...

http://stackoverflow.com/questions/1143783/debug-breakpoint-doesnt-work-only-in-
datamodule-unit-delphi

Original comment by linards....@gmail.com on 22 Mar 2012 at 4:51

GoogleCodeExporter commented 9 years ago 
And finally:

http://stackoverflow.com/questions/2343875/disassembling-a-dll-coded-in-delphi-h
ow-to-start

Original comment by linards....@gmail.com on 22 Mar 2012 at 5:05

GoogleCodeExporter commented 9 years ago 
I assume that this utilities source can be used to import portions for BPL 
disassembly and therefore power to have Package support :)

http://www.woodmann.com/collaborative/tools/index.php/DeDe

Hope I helped by gathering this info...

Original comment by linards....@gmail.com on 22 Mar 2012 at 5:10

GoogleCodeExporter commented 9 years ago 
This should be set to HIGH priority iisue! :)

Original comment by linards....@gmail.com on 27 Mar 2012 at 12:10

GoogleCodeExporter commented 9 years ago 
Since BPLs are regular DLLs, I suspect what needs to happen is to catch the 
loading (HandleLoadDLL in Debugger.pas) and addBreakPoints corresponding to 
that BPL just loaded. It might be relatively easy to implement, unfortunately I 
don't have the time at the moment to try it out.

Original comment by christer...@gmail.com on 27 Mar 2012 at 3:33

GoogleCodeExporter commented 9 years ago 
Just wanned to add note that the support for this feature is now under testing 
/ debugging. Stay tuned...

Original comment by linards....@gmail.com on 20 Apr 2012 at 9:32

GoogleCodeExporter commented 9 years ago

Original comment by linards....@gmail.com on 23 Apr 2012 at 2:43