Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong line numbers on CPU64 #76

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

keksoid
Copy link

@keksoid keksoid commented Nov 22, 2019

I did few tests on small projects and quite big ones including reccursion and noticed, that line numbers're calculated with offset = 2. And it seems to me, that this is a constant value. And tests prove that. Actually I don't have enough experience to find better solution, but I suppose, you do. This error could lead into more complicated errors, because .CallerAddr is used widely. I'dont think, that mistake is located inside CaptureStackBackTrace(internal RtlCaptureStackBackTrace). It's also could be an Embarcadero bug dcc64 but, as far as I know, it's written completely from zero.

I did few tests on small projects and quite big ones including reccursion and noticed, that line numbers're calculated with offset = 2. And it seems to me, that this is a constant value. And tests prove that. Actually I don't have enougth experience to find better solution, but I suppose, you do. This error could lead into more complicated errors, because .CallerAddr is used widely. I'dont think, that mistake is located inside CaptureStackBackTrace(internal RtlCaptureStackBackTrace). It's also could be an Embarcadero bug dcc64 but, as far as I know, it's written completele from zero.
@MHumm
Copy link
Contributor

MHumm commented Dec 30, 2019

What about FPC? Is this the same for that as well? Has any attempt been made to clarify whether the issues comes from a EMBT DCC64 bug or from JCL itsself?

@MHumm
Copy link
Contributor

MHumm commented Aug 9, 2020

@keksoid have you already looked into quality.embarcadero.com to check if this is actually a DCC64 bug which is already known? Would you please do that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants