Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] Patch to improve error messages

On Mon, Mar 31, 2008 at 7:52 PM, John Cortell
<john.cortell@xxxxxxxxxxxxx> wrote:
> At 12:28 PM 3/31/2008, Øyvind Harboe wrote:
>  >Hi John,
>  >
>  >excuse my ignorance, but are you a committer?
>
>  I am.
>
>
>  > >  Can you explain how to reproduce the problem. If
>  > >  I remove the executable of a simple project
>  > >  before launching a debug session, I get an error
>  > >  dialog that needs improved grammar, but isn't
>  > >  completely nonsensical or cryptic (see attached
>  > >  screenshot). I assume your scenario is different.
>  > >  It's important to provide reproducibility steps
>  > >  when you submit a patch (if possible; sometimes,
>  > >  a bug can be seen with a particular backend but
>  > >  not the standard gnu/cygwin ones.
>  >
>  >Are you in agreement that, fundamentally, error messages
>  >should be propagated and not anonymized?
>
>  I am.
>
>
>
>  > >  And of course, the formal process is to create a bugzilla report.
>  >
>  >I've tried that for lots of patches through the years. I'm trying something
>  >a bit different this time to see if I have any better luck. It's an experiment
>  >if you will.
>
>  I'm not sure you're going to have much success
>  since ultimately someone should be opening a
>  bugzilla report. All you're doing is making more work for committers
>
>  Interestingly, you didn't supply the key piece of
>  information I requested. Reproducibility steps.

I understand from the above that you agree that it has been determined
that this is broken by inspection(and some cursory testing).

Surely it's not necessary to reproducability steps any more than
e.g. fresh regression testing cases for code that it is agreed is
broken by inspection?

I'll open a bugzilla report for this problem if there is consensus that
this should be fixed and that it can be agreed upon that it is broken.

In terms of testcase/reproducability, I'd go for a JUnit(or equivalent) test
for something like this. I don't know how to formulate such a test.




-- 
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit


Back to the top