This is a new set of potential bugs found via Viva64:
Example 1. ReactOS project. Incorrect printing of a WCHAR-character( regproc.c 293) .
static void REGPROC_unescape_string(WCHAR* str)
{
...
default:
fprintf(stderr,
"Warning! Unrecognized escape sequence: \\%c'\n",
str[str_idx]);
...
}Reason: To fix the code, we should replace '%c' with '%C' in the format string.
Example 2. ReactOS project. Assignment error. (menu.c 4347)
BOOL WINAPI GetMenuItemInfoA(...)
{
...
mii->cch = mii->cch;
...
}
Example 16. ReactOS project. Misprint in a macro.( win32k gradient.c 343 )
#define SWAP(a,b,c) c = a;\
a = b;\
a = c
Example 8. ReactOS object. Choosing a wrong object.
void CardButton::DrawRect(HDC hdc, RECT *rect, bool fNormal)
{
...
HPEN hhi = CreatePen(0, 0, MAKE_PALETTERGB(crHighlight));
HPEN hsh = CreatePen(0, 0, MAKE_PALETTERGB(crShadow));
...
if(fNormal)
hOld = SelectObject(hdc, hhi);
else
hOld = SelectObject(hdc, hhi);
...
}
The 'then' statement is equivalent to the 'else' statement. cardlib cardbutton.cpp 83
The 'hsh' object is not used, while 'hhi' is used twice. This is the correct code:
if(fNormal)
hOld = SelectObject(hdc, hhi);
else
hOld = SelectObject(hdc, hsh);
Example 10. ReactOS project. Mistake in a variable name.
BOOL APIENTRY
GreStretchBltMask(...)
{
...
MaskPoint.x += DCMask->ptlDCOrig.x;
MaskPoint.y += DCMask->ptlDCOrig.x;
...
}
Consider reviewing the correctness of 'x' item's usage. win32k bitblt.c 670
Example 4. ReactOS project. Incorrect calculation of a string length ( vbe.c 57 )
static const PCHAR Nv11Board = "NV11 (GeForce2) Board";
static const PCHAR Nv11Chip = "Chip Rev B2";
static const PCHAR Nv11Vendor = "NVidia Corporation";
BOOLEAN
IsVesaBiosOk(...)
{
...
if (!(strncmp(Vendor, Nv11Vendor, sizeof(Nv11Vendor))) &&
!(strncmp(Product, Nv11Board, sizeof(Nv11Board))) &&
!(strncmp(Revision, Nv11Chip, sizeof(Nv11Chip))) &&
(OemRevision == 0x311))
...
}Reason: The error here is this: the sizeof() operator, absolutely inappropriate
in this situation, is used to calculate string lengths. The sizeof()
operator actually calculates the pointer size instead of the number of
bytes in a string.
In this case Abragin said this is not a bug.
I'm sending here to discuss about them ;).Are they valid?
Link: http://www.viva64.com/en/a/0079/
Automatic Continue in kdb has been implemented and improves the debugging on the test bots.
However, the KVM bot can't use it in the first stage because it is controlled by keyboard entries at this time.
I propose to switch the first stage to kdserial as well.
Any objections ?
Kind regards,
Sylvain Petreolle
..\..\dll\win32\avifil32\avifile_Hu.rc(32) : error RC2101 : invalid directive in preprocessed RC file
Still broken, since winesync
Best regards
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Date: Thu, 15 Mar 2012 23:12:01 +0000
Subject: buildbot failure in ReactOS on CMake_x86_MSVCWin Debug
The Buildbot has finished a build on builder CMake_x86_MSVCWin Debug while building ReactOS.
Full details are available at:
http://build.reactos.org/builders/CMake_x86_MSVCWin%20Debug/builds/808
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_1
Build Reason: scheduler
Build Source Stamp: 56167
Blamelist: rharabien
BUILD FAILED: failed building bootcd
sincerely,
-The Buildbot
--
With best regards
Caemyr
On Mar 11, 2012, at 7:13 AM, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Sun Mar 11 11:13:15 2012
> New Revision: 56113
>
> URL: http://svn.reactos.org/svn/reactos?rev=56113&view=rev
> Log:
> [HIVESYS]
> - Merge back many old changes from i386 to AMD64
The way we do hive INFs is very far from ideal right now. I propose to create a base INF that is used to construct each hive and turning the hivexxx_arch.inf into an additional section like livecd.inf is now. This way every architecture inherits a base configuration and turning on/off services or changing certain settings can be done in the arch-specific inf. This would eliminate having to do these merge backs and also prevent tons of breakages and lost time in the future from having to merge the same change 3+ times.
Regards,
Cameron
FYI
-------- Original Message --------
Hi there,
Someone recommended that I point out my open-source INI editor for
Reactos... Here it is:
http://code.google.com/p/ini-settings-editor/
It opens INI files into a pretty tab-based view for editing.
Let me know if you have any comments about it.
Added yet another check, this time for all builders, which will stop any run passed without revision number.
On Sat, Mar 10, 2012, at 05:34 AM, buildbot(a)reactos.org wrote:
> The Buildbot has finished a build on builder Windows_AMD64_1 VBox-Test
> while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/5238
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger)
> Build Source Stamp: 56097
> Blamelist:
>
> BUILD FAILED: failed Initial preparations
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr
Strange vbox lockup at the end of 2nd stage. Build restarted, went fine this time.
On Sat, Mar 10, 2012, at 01:24 AM, buildbot(a)reactos.org wrote:
> The Buildbot has finished a build on builder Windows_AMD64_1 VBox-Test
> while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/5236
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: Triggerable(Windows_AMD64_1 VBox-Test Trigger)
> Build Source Stamp: 56096
> Blamelist: spetreolle
>
> BUILD FAILED: exception test
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr