Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/Debugger/Breakpoints    [ Add a report in this area ]  
Report #:  105861   Status: Closed
Breakpoints stop functioning if code contains incomplete CRLF sequence
Project:  Delphi Build #:  16.0.4504.48759
Version:    16.4 Submitted By:   Dalija Prasnikar
Report Type:  Basic functionality failure Date Reported:  5/24/2012 4:25:09 AM
Severity:    Infrequently encountered problem Last Updated: 7/18/2012 12:56:11 AM
Platform:    All versions Internal Tracking #:   28497
Resolution: Won't Do (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Breakpoints stop functioning properly if code contains incomplete CRLF sequence
Steps to Reproduce:
1. Set Options -> Source Options -> show line breaks
2. Open attached project
3. Set two breakpoints - both on lines x := 5;
4. Run project
5. Step through code with F8 - it works until it hits second breakpoint that is set in line containing incomplete CRLF, and after that it doesn't work anymore

Tomohiro Takahashi at 5/25/2012 12:46:37 AM -
This report was opened with valid Internal Tracking Number.

Dalija Prasnikar at 7/22/2012 4:40:37 AM -

I can see that this report is closed as "Won't Do". I don't have problem with that resolution, because cause of the problem lies elsewhere. There are other bug reports caused by incomplete CRLF sequences and IMHO the only proper solution to that problem (instead of fixing every part of the IDE to work with them) is to correct the problem at its core. And that is adding functionality to the editor to auto correct incomplete CRLF sequences as it encounters it as proposed in QC #105862. But that report is not even Opened.

It is very easy to end up with code that doesn't have proper CRLF line endings (it has even happened in VCL source QC #105863), and it is very hard to work when suddenly IDE starts behaving crazy and you don't have a clue what is the cause.

If proposed solution of auto fixing line endings is not acceptable, then at least consider adding some visible marker that can warn programmers they are dealing with code that has inproper line endings.

Thank you.

Tomohiro Takahashi at 7/23/2012 5:52:27 PM -
Thanks for the notification. I will check why this report was closed 'Won't Do'.

Tomohiro Takahashi at 7/23/2012 5:53:43 PM -
This is a comment from internal tracking system.
Our editor requires source files to be consistent with the end of line sequences. Without this, the compiler doesn't know what line the source text is on. You can use a text editor program to convert the source file to Windows format and this will resolve the issue.

Dalija Prasnikar at 7/24/2012 4:47:05 AM -
Thank you for the response.

I understand the need for consistent line endings. Currently the problem is that Delphi IDE doesn't give you any signals that you have incomplete line endings and it doesn't automatically fix them.

Could you please open QC 105862 because it would be the best solution for the problem. Or give me any other directions how to proceed in this matter because this problem is not going away.

It is not a problem to open source in some other editor and fix line endings. The problem is that you usually don't know you have wrong line endings. IMO some kind of warning system would be mandatory.

Alex Alexeev at 12/15/2014 4:07:33 PM -
Why can't it be fixed just doing AdjustLineBreaks when opening .pas file?

Server Response from: ETNACODE01