| View previous topic :: View next topic |
| Author |
Message |
David Intersimone David I Guest
|
Posted: Thu Sep 29, 2005 1:29 pm Post subject: DeXter C++ Quality Central bugs resolved so far... |
|
|
John Kaster has updated C++Builder Quality Central reports with DeXter C++
fixed status (so far). He will be updating the QC reports periodically as
the builds continue. To see the fixed list, use the following QC query.
http://qc.borland.com/wc/qcmain.aspx?search=1&proj=15&rib=+10.0.2097.6343
|
|
| Back to top |
|
 |
Jeff Overcash (TeamB) Guest
|
Posted: Thu Sep 29, 2005 3:01 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
David Intersimone "David I wrote:
There have acutely been a few other pulls (on other builds #s) so if you search
on just resolved in build 10 you will get more results.
http://qc.borland.com/wc/qcmain.aspx?search=1&proj=15&rib=10
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Your friends will know you better in the first minute you meet than your
acquaintances will know you in a thousand years. (R Bach)
|
|
| Back to top |
|
 |
Randall Parker Guest
|
Posted: Thu Sep 29, 2005 5:35 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
This list makes me hopeful. But I do not see evidence they've fixed what bothers me
most often:
1) Internal compiler error on TComModule line.
2) Debugger stops working and tds file must get deleted.
I've seen this one a lot:
BCB6 Upd2 introduced error: 'Public symbol ... defined on both module ... and ...'
I've also seen the one where the whole project gets rebuilt even though you do a Run
and not much has changed.
I wonder if the linker errors are for fixes that were done after the last linker release.
Everyone be sure to note that there is a second page selectable at the bottom.
Jeff Overcash (TeamB) wrote:
|
|
| Back to top |
|
 |
Jeff Overcash (TeamB) Guest
|
Posted: Thu Sep 29, 2005 5:42 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Randall Parker wrote:
| Quote: |
This list makes me hopeful. But I do not see evidence they've fixed what bothers me
most often:
|
a) it is not a complete list
b) many internal only reports have been fixed, but not made public.
c) not all QC entries are promoted because they are already in the internal DB.
I'm not going to comment on personal pet bugs, but the fact that something is
not in the list yet does not mean that a) it hasn't been address or b) they
still plan on addressing it.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Your friends will know you better in the first minute you meet than your
acquaintances will know you in a thousand years. (R Bach)
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Thu Sep 29, 2005 5:54 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Randall Parker wrote:
| Quote: | This list makes me hopeful. But I do not see evidence they've fixed what
bothers me most often:
1) Internal compiler error on TComModule line.
Randall, is there a QC number for this? If not, a short test case? |
..a
|
|
| Back to top |
|
 |
Tamas Demjen Guest
|
Posted: Thu Sep 29, 2005 6:03 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Randall Parker wrote:
| Quote: | This list makes me hopeful. But I do not see evidence they've fixed what
bothers me most often:
1) Internal compiler error on TComModule line.
2) Debugger stops working and tds file must get deleted.
|
I agree. Those are the two main problems I get often too. Sometimes it's
enough to close the project, sometimes I have to delete the TDS file and
rebuild to fix them.
| Quote: | I've also seen the one where the whole project gets rebuilt even though
you do a Run and not much has changed.
|
It has three aspects:
- Any slight modification you make to the project options (such as
increase the version number) triggers a full rebuild. BCB5 and earlier
didn't do that.
- If you have a .pas in the project, the IDE always regenerates the .hpp
file, which makes the project manager believe they changed and every
unit that includes it will be recompiled (even if no modifications were
made to the .pas file).
- If you have a type library in the project, the IDE always updates the
auto-generated .h files, which again triggers a recompile to every unit
that includes them (even when no modifications were made to the type
library).
Tom
|
|
| Back to top |
|
 |
Randall Parker Guest
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Thu Sep 29, 2005 6:45 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Randall Parker wrote:
| Quote: | Alex,
I'm searching QC and do not see an entry for it. Mind you, I'm not sure
if I'm setting up the searches correctly. With the web page do you have
to select something from every list box? Isn't there a "don't care"
method of doing this? Why make someone select a single BCB version if
the original report could have been filed 2 versions ago?
I don't really know how that search is supposed to work  |
| Quote: | This error comes up occasionally. I can never predict when it will
happen. I can not create a test case since I do not know how to make it
happen. Sometimes it'll happen to me 5 times in a day and other times
I'll go weeks without seeing it. I have to build all to get around it.
Hmm, I understand, but that will make a fix so much less probable. |
Hopefully, this is going to be fixed incidentally with other ICE fixes.
Cheers,
..a
p.s. have you applied for the beta?
|
|
| Back to top |
|
 |
vavan Guest
|
Posted: Mon Oct 03, 2005 11:44 am Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
On Thu, 29 Sep 2005 13:42:07 -0400, "Jeff Overcash (TeamB)"
<jeffovercash (AT) mindspring (DOT) com> wrote:
| Quote: | a) it is not a complete list
b) many internal only reports have been fixed, but not made public.
c) not all QC entries are promoted because they are already in the internal DB.
I'm not going to comment on personal pet bugs, but the fact that something is
not in the list yet does not mean that a) it hasn't been address or b) they
still plan on addressing it.
|
I'm not very satisfied with _how_ they "fixed" some of those bugs -
see for example qc#6978
--
Vladimir Ulchenko aka vavan
|
|
| Back to top |
|
 |
Jeff Overcash (TeamB) Guest
|
Posted: Mon Oct 03, 2005 4:19 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
vavan wrote:
| Quote: |
I'm not very satisfied with _how_ they "fixed" some of those bugs -
see for example qc#6978
|
If you are not satisfied with how they "fixed" some bugs, at least present a QC
entry that is marked fixed. This one is clearly marked as a "test case error".
Read Remy's explanation on why it is a test case error, this is exactly what the
R&D engineer agreed with in the internal report. Borland does not claim to have
fixed 6978, only that it was closed due to a test case error.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Your friends will know you better in the first minute you meet than your
acquaintances will know you in a thousand years. (R Bach)
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Mon Oct 03, 2005 4:52 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Jeff Overcash (TeamB) wrote:
| Quote: |
If you are not satisfied with how they "fixed" some bugs, at least present a QC
entry that is marked fixed. This one is clearly marked as a "test case error".
Read Remy's explanation on why it is a test case error, this is exactly what the
R&D engineer agreed with in the internal report. Borland does not claim to have
fixed 6978, only that it was closed due to a test case error.
|
Hmm, that's not a test case error. Remy's explanation is incorrect.
..a
|
|
| Back to top |
|
 |
Jeff Overcash (TeamB) Guest
|
Posted: Mon Oct 03, 2005 5:30 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
"Alex Bakaev [TeamB]" wrote:
| Quote: |
Hmm, that's not a test case error. Remy's explanation is incorrect.
|
Well the internal comment on this by the R&D engineer agrees with Remy's
assessment. That is why it was closed as a test case error by the engineer (not
by Remy).
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Your friends will know you better in the first minute you meet than your
acquaintances will know you in a thousand years. (R Bach)
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Mon Oct 03, 2005 10:27 pm Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Jeff Overcash (TeamB) wrote:
| Quote: | Well the internal comment on this by the R&D engineer agrees with Remy's
assessment. That is why it was closed as a test case error by the engineer (not
by Remy).
I don't think I have access to the internal comment, so I go only by |
what's in QC.
..a
|
|
| Back to top |
|
 |
Jeff Overcash (TeamB) Guest
|
Posted: Tue Oct 04, 2005 12:14 am Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
"Alex Bakaev [TeamB]" wrote:
| Quote: |
Jeff Overcash (TeamB) wrote:
Well the internal comment on this by the R&D engineer agrees with Remy's
assessment. That is why it was closed as a test case error by the engineer (not
by Remy).
I don't think I have access to the internal comment, so I go only by
what's in QC.
|
My point is still the same. Borland never claimed to have fixed this. The
original complaint was that he didn't agree with the fix, but Borland never
claimed they did anything about this. You can claim that it is not a test case
error and I won't argue with you, but if you want to hold this up as an example
of a "fix" by Borland I will argue because this is not something Borland claimed
to have fixed in any way.
--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
Your friends will know you better in the first minute you meet than your
acquaintances will know you in a thousand years. (R Bach)
|
|
| Back to top |
|
 |
Alex Bakaev [TeamB] Guest
|
Posted: Tue Oct 04, 2005 12:48 am Post subject: Re: DeXter C++ Quality Central bugs resolved so far... |
|
|
Jeff Overcash (TeamB) wrote:
| Quote: |
My point is still the same. Borland never claimed to have fixed this. The
original complaint was that he didn't agree with the fix, but Borland never
claimed they did anything about this. You can claim that it is not a test case
error and I won't argue with you, but if you want to hold this up as an example
of a "fix" by Borland I will argue because this is not something Borland claimed
to have fixed in any way.
Oh, I'm not arguing fixed vs. unfixed. But as it stands, the bug still |
seems to exist - and I understand that to be the concern of the OP.
..a
|
|
| Back to top |
|
 |
|