Line numbers not appearing in Runtime packages

[NeilRobinson]

I'm in the process of evaluating EurekaLog to be used with our D7 application and I've running into a problem getting the line numbers to show with our runtime packages.

Now, it does work correctly on the main exe (which is really just a stub), and it still shows the call stack on the run-time packages, but not the line numbers.

However, if I compile each run-time package manually though the IDE then I see the line numbers in EurekaLog.

When I do my batch compile I am calling ecc32, and passing in the same configuration file (.eof) to every package and the main exe.

Thank you,

Neil

[admin]

NeilRobinson wrote:
> I'm in the process of evaluating EurekaLog to be used with our D7
> application and I've running into a problem getting the line numbers to
> show with our runtime packages.
>
> Now, it does work correctly on the main exe (which is really just a
> stub), and it still shows the call stack on the run-time packages, but
> not the line numbers.
>
> However, if I compile each run-time package manually though the IDE
> then I see the line numbers in EurekaLog.
>
> When I do my batch compile I am calling ecc32, and passing in the same
> configuration file (.eof) to every package and the main exe.
>
> Thank you,
>
> Neil

Can you send to me the batch and .eof files used, so that I'll can
analyze those and tell back to you what's wrong, please? :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG showing line n.

[NeilRobinson]

Thank you Fabio. I have sent you an email.

Neil

[admin]

NeilRobinson wrote:
> Thank you Fabio. I have sent you an email.
>
> Neil

I have tested your files and all works fine.

So I suggest to try to do this:

1)...Close all opened Delphi/CBuilder instances;
2)...Deinstall all installed EurekaLog versions;
3)...Remove all folders containing the ExceptionLog.* or
?ExceptionExpert.* files;
4)...download and install the last EurekaLog version;
5)...restart your PC.

I'm waiting to your feedback as soon as possible, ok? :)


--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG showing line n.

[NeilRobinson]

I've reinstalled and I'm still getting the same problems. I'm waiting to get the full edition of the software (once the company director approves it) and then I'll test it out again.

Neil

[admin]

NeilRobinson wrote:
> I've reinstalled and I'm still getting the same problems. I'm waiting to
> get the full edition of the software (once the company director
> approves it) and then I'll test it out again.
>
> Neil

Ok, I'm waiting for your feedback ASAP! :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG showing line n.

[NeilRobinson]

An update.

I've gotten it all working. It seems that there is a difference depending on whether you are compiling from the IDE or the the command line.

DCC32 compiler - uses .CFG file for settings
IDE compiler - uses .DOF File for settings

What I had in the .DOF was correct, but the project .CFG file was incorrect. I made a standard .CFG file for all my BPLs and suddenly the line numbers were showing up everywhere.

Neil

[admin]

Hi,

NeilRobinson wrote:
> An update.
>
> I've gotten it all working. It seems that there is a difference
> depending on whether you are compiling from the IDE or the the command
> line.
>
> DCC32 compiler - uses .CFG file for settings
> IDE compiler - uses .DOF File for settings
>

Yes, it's so!

>
> What I had in the .DOF was correct, but the project .CFG file was
> incorrect. I made a standard .CFG file for all my BPLs and suddenly the
> line numbers were showing up everywhere.
>
> Neil

Perfect! :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG showing line n.