Jump to content


Guidelines For A Good Bug Report


4 replies to this topic

#1 Guest_Pavel_*

Guest_Pavel_*
  • Guests

Posted 07 March 2003 - 11:01 PM

A good bug report serves three major purposes: to explain a problem, to describe steps to reproduce the problem and to explain what is the expected behavior. When a new report is submittet please try to include all these parts  into it.

Below is a suggested bug report format:

Bug description:
A bug description

Steps to reproduce:
Detailed description to reproduce this problem (may contain source code and output log)

Expected behaviour:
How a fixed program should behave.

Is the problem 100% reproduceable:
does this problem happens every time, sometimes, very rare

IDE version:   SourceBoost IDE version
Compiler:               Compiler (BoostC, C2C-plus, C2C++ or P2C-plus)
Compiler version:     Compiler version
Target device: PICXXXXX
OS:                      OS version

Comments:
Extra information that doesn't fit into other report fields


Regards,
Pavel

#2 Coder

Coder

    Newbrie

  • EstablishedMember
  • 8 posts

Posted 14 April 2010 - 09:04 PM

Hi Pavel,

ok, nice description. But i'm missing a description of what is done after we report a bug.

Would be nice to get a little statement like:
- Bug could be reproduced
- Solved at version...
....
Something like that.

Will that be done?

Greetings
Coder

#3 Pavel

Pavel

    Super Maniac

  • Administrators
  • PipPipPipPipPip
  • 1,441 posts
  • Gender:Male
  • Location:Melbourne, Australia

Posted 16 April 2010 - 01:00 AM

ok, nice description. But i'm missing a description of what is done after we report a bug.

Would be nice to get a little statement like:
- Bug could be reproduced
- Solved at version...
....
Something like that.

Will that be done?


Sometimes we do. But we don't plan to do it for every post. The idea of these posts is to let us know about the problems. These problems than go into our bug tracking system that we use internally.

Regards,
Pavel

#4 rgammage

rgammage

    Newbrie

  • Members
  • 2 posts

Posted 19 March 2017 - 10:37 AM

A good bug report serves three major purposes: to explain a problem, to describe steps to reproduce the problem and to explain what is the expected behavior. When a new report is submittet please try to include all these parts  into it.

Below is a suggested bug report format:

Bug description:
A bug description

Steps to reproduce:
Detailed description to reproduce this problem (may contain source code and output log)

Expected behaviour:
How a fixed program should behave.

Is the problem 100% reproduceable:
does this problem happens every time, sometimes, very rare

IDE version:   SourceBoost IDE version
Compiler:               Compiler (BoostC, C2C-plus, C2C++ or P2C-plus)
Compiler version:     Compiler version
Target device: PICXXXXX
OS:                      OS version

Comments:
Extra information that doesn't fit into other report fields


Regards,
Pavel

Following the above .......

 

The creation of arrays seems to be at fault.

 

unsigned char Array[5]  ........   should produce 6 locations 0 - 5

 

Array[5] = '5';                    should put '5' into array at location 5

 

a = Array[5];                      In this example 'a' will not be '5' 

 

If the array is made larger say ... static char Array[6] then Array[5] works as it should and I assume Array[6] is now faulty but I have not checked. The contents are constant, nott varying, and so are being read from somewhere.

 

IDE version:              SourceBoost IDE version 7.30
Compiler:                  BoostC 7.30
Compiler version:     Compiler version
Target device:           PIC18F66k80
OS:                           W10

 

Is this product still being supported? There seems to be so liitle activity on this site for what is an excellent product.  If activity is to stop can you release details of how to create the include files etc. for new products? I did have a go a few years ago without success.

 

Regards

 

Richard



#5 Reynard

Reynard

    Maniac

  • EstablishedMember
  • PipPipPipPip
  • 660 posts
  • Gender:Male
  • Location:Scotland
  • Interests:Archery - target and field

Posted 20 March 2017 - 09:35 AM

Hi Richard,

 

Array[5] says you are asking for an array of 5 chars therefor 0 - 4 are the indexes.

 

Yes it is a good product but needs to be brought up to date with the editor and a few bug fixes, 64 bit version etc.

 

I am still using it today along with Novo.

 

Cheers

 

Reynard





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users