[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 274502] Debugger does not handle empty else clause
From:       Ron <iampure () gmail ! com>
Date:       2011-05-30 17:09:57
Message-ID: 20110530170957.2AA7486682 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=274502


Ron <iampure@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |




--- Comment #2 from Ron <iampure gmail com>  2011-05-30 19:09:56 ---
No, I am not compiling with optimizations, in fact, I am compiling with --ggdb3
and -O0. 

Now, something which annoys me in your response. I take the time to report a
bug, and you close it as if it is INVALID without consulting me. It is not
INVALID. It might be that you have a different idea of what a bug is, but I am
the user here, so I know whether or it is a feature I want. 

Let me elaborate a bit on that. The fact that you use GDB is a mere
_implementation_ detail. KDevelop4 has a feature to put a breakpoint on a line.
Clearly, this feature is not working as I demonstrated above. So, it is a bug.
There is nothing INVALID about it. 

Now, you could say that you want to build an application in which you promise
things in the GUI, but which then do not work, but then all you have is a buggy
application. 

Again, just saying that GDB does it in a certain way, is _completely_
irrelevant. You (as in the KDevelop4 developers) decided to use GDB to
implement a feature. If you cannot make GDB do whatever the user requested,
then _do_not_use_it_ in your implementation. Simple. 

One correct way to fix this in to implement your own debugger, but there are
simpler ways. If you cannot think of a way to solve this issue, it does _not_
mean  nobody can. 

It is a bug, so either just kill the entire line oriented debugging feature (no
feature implies no bugs), or write some decent software.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]