Bug#39036: marked as done (debugger code window current line handling is incorrect when carriage returns CR are present) by John Firebaugh <jfirebaugh at kde.org>

Stephan Kulow owner at bugs.kde.org
Sat Aug 31 08:49:50 UTC 2002

Your message with subj: debugger code window current line handling is incorrect when carriage returns CR are present

Thank you for your bug report.
The bug that your reported no longer applies to the latest development (CVS) 
version of KDE. This is most probably because the bug has been fixed, the 
application has been substantially modified, or the application no longer 
exists. The bug report will be closed.

has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

(Complete bug history is available at http://bugs.kde.org/db/39/39036.html)

Received: (at submit) by bugs.kde.org; 6 Mar 2002 16:15:30 +0000
Received: (qmail 13972 invoked by uid 33); 6 Mar 2002 16:15:29 -0000
Date: 6 Mar 2002 16:15:29 -0000
Message-ID: <20020306161529.13971.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: debugger code window current line handling is incorrect when carriage returns CR are present
From: Virgil at Nomadics.com
X-KDE-Received: -

Package:           kdevelop
Version:           2.0.2 (using KDE 2.2.2 -2)
Severity:          normal
Installed from:    Red Hat Linux 7.2
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:                Linux (i686) release 2.4.7-10
OS/Compiler notes: 

When a code file containing CR LF pairs (DOS style newlines) is used to compile a program, and then that program is debugged the current line prompt is often incorrect and breakpoints fail to be associated with the proper line of code.

Unfortunately, this behavior does not seem as simple as to imply that the IDE miscounts a line at every CR.  However, I've seen this extremely frequently when utilizing a file created using MSVC and occassionally edited with KDevelop.

In fact while I have not confirmed it this bug may well stem from some attempt to special case DOS style files that fails if the newline encoding is not consistent in the file.

In all observed cases stripping all CRs out of the file put an end to the behavior.

I personally assert that the best way to handle this old annoying issue is to interpret a line as ending at either a CR or a LF, but then if it is a CR check the next character and bypass it if it is a LF.

However, the issue in this specific case is that the IDEs line-counting differs from that of gdb and therefore there is confusion in the communications between the IDE and the debugger.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)

More information about the KDevelop-devel mailing list