Bugzilla – Full Text Bug Listing
| Summary: | Disassembly view is broken in 3.5.2 and CDT 6.0.2 | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Omry Yadan <public> |
| Component: | cdt-debug | Assignee: | cdt-debug-inbox <cdt-debug-inbox> |
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> |
| Severity: | major | ||
| Priority: | P3 | CC: | aegges, aleherb+eclipse, cdtdoug, malaperle, marc.khouzam, markdigitalchips, pawel.1.piech, zulliger |
| Version: | 6.0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Omry Yadan
updated version Wrong component I can also reproduce this on Windows (Vista 64 + MinGW). ...with CDT 8.0.2 RC2 (In reply to comment #4) > ...with CDT 8.0.2 RC2 Still reproducable on Linux with CDT 8.2 it's only been 3 years. other eclipse bugs that I reported are are still open after 9 years. https://bugs.eclipse.org/bugs/show_bug.cgi?id=76646 https://bugs.eclipse.org/bugs/show_bug.cgi?id=114003 Sad to say, but Eclipse smells a kind of dead. (In reply to comment #6) > it's only been 3 years. other eclipse bugs that I reported are are still > open after 9 years. > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=76646 > https://bugs.eclipse.org/bugs/show_bug.cgi?id=114003 > > Sad to say, but Eclipse smells a kind of dead. A bug that has no activity for many years will not attract any attention. If you care about a bug it may help to (politely) ping on the bug, or ask if you can help, or something of the kind. The idea is to bring the bug back into the spotlight and let people know someone cares about it being fixed. This is no bug IMO. The Disassembly editor cannot be used for ordinary files. It is solely used as a disassembly view for an active debug context. I don't see "Disassembly" in the Open with... menu of binary files. I have to choose Other... and then select "Disassembly", but I could as well select any other useless editor, like "Source Not Found" or "Class File Viewer", etc. Marc, I did not mean to insult, just pointing out that it looks like Eclipse lose all it's early momentum. I opened this bug because this seems like, well - a bug, and I care about Eclipse. many people after me mentioned that they encountered it too, and cared enough to find this and mentioned that they are still seeing it and have tried to bring it into the spotlight politely. (see all the "me too" comments). Anton, this is CLEARLY a bug. ClassCastException triggered by a UI action is a bug, no matter how you spin it. You raise a great point Omry. Enough that I've actually blogged about it. http://cdtdoug.blogspot.ca. And you are right, Eclipse has lost a lot of steam and we need to figure out how to light the fire again. But it's certainly not dead as you can see by the number of CDT committers that are responding here :) (In reply to comment #9) > Marc, > I did not mean to insult, just pointing out that it looks like Eclipse lose > all it's early momentum. No insult taken. I understand your frustration and was trying to give hints on how you can help get your bugs resolved. > I opened this bug because this seems like, well - a bug, and I care about > Eclipse. Thank you for that. Users that take the time to open bugs should at least get feedback to reward their efforts. I will personally try to be better at that in the future. > many people after me mentioned that they encountered it too, and cared > enough to find this and mentioned that they are still seeing it and have > tried to bring it into the spotlight politely. (see all the "me too" > comments). Sorry, I didn't mean to imply there was impoliteness in this case. I just mentioned politeness because I personally don't like when people just write "PING!", which I've seen before. I just didn't want someone to come back and say "But Marc K said to ping the bug, which I did" :) > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=76646 > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=114003 I was referring to the above two bugs. The first has its last activity in April 2004, while the second has been touched since November 2006. Speaking for myself, when faced with a huge backlog of bugs, many of which are no longer applicable, I will rarely look at old bugs, simply because newer bugs have an increased chance of being valid. However, if someone goes back to the bug to say "still happening with version xyz", it pushes the bug up the list, and confirms that someone still is bothered by it. I can't promise anything, but it is good to get committers to think about this situation. I hope it will help us improve the CDT community and satisfaction. (In reply to comment #9) > Anton, this is CLEARLY a bug. > ClassCastException triggered by a UI action is a bug, no matter how you spin > it. So perhaps this bug should be about improving the error message? From what I understand, if you want to see the disassembly of a binary, you would only have to double click on the binary which would open the "Default Binary File Editor". Unfortunately, this editor has a few problems too which we could address in separate bugs: - It doesn't work on archives (.a) - It doesn't seem to work with all toolchains. I got it working only with Cygwin Marc K, those two bugs of mine were just my oldest open bugs. not the most important to fix. one is pretty much irrelevant (almost no one uses CVS these days, maybe it's just time to deprecate CVS in Eclipse). the other one seems solved (on a vanila new installation of Eclipse, new files no longer has the annoying comment on how to change the annoying comment). I will post a comment on your blog post, I have a lot to say which is not relevant to this bug. Marc L: If, product wise - this is actually not supposed to be supported (I have a sense that it did used to work but after 3 years who knows) - then I am of course fine with removing the UI option or otherwise making sure a user does get an internal Eclipse error. |