Sorry but these kinds of fixes are not "readability fixes", in fact they
make things more obtuse.
(*MdlPages << PAGE_SHIFT)) could be interpreted as
*(MdlPages << PAGE_SHIFT).
while
((*MdlPages) << PAGE_SHIFT)
Makes it clear what is happening.
In general, all operations affecting the contents of a *dereference should
be in parens.
Best regards,
Alex Ionescu
On Sun, Sep 11, 2011 at 7:47 AM, <tfaber(a)svn.reactos.org> wrote:
> - ((*MdlPages) << PAGE_SHIFT));
> + (*MdlPages << PAGE_SHIFT));
>
Hi all,
Andrey Karpov of "SiProVer" Ltd (www.viva64.com/ ), the authors of
PVS-Studio, a
statical source code analyzer/checker wrote (in Russian, this
translation is conducted by me):
"Have checked source code of ReactOS with PVS-Studio, I fulfilled
three wishes of mine at once:
Firstly, for a long time I wanted to write an article about ordinary
project. It
is not so interesting to check source code of such projects as Chromium,
It is of too high quality and resources are spending for keeping this level of
quality, resources which are unavailable to ordinary projects.
Secondly, ReactOS appears to be a good example of project, for which high
need of statical analysis of source code can be shown, especially as project
being developed with distributed team of developers with diversely
different experience.
Thirdly, I got confirmation of PVS-Studio getting better and better
and more useful
all along the way..."
Full text of original Russian article is here:
http://habrahabr.ru/blogs/os/127493/
titled on Russian as "PVS-Studio: analysing ReactOS operating system
source code".
Evgeniy Ryzhkov of "SiProVer" adds:
"Soon we will translate and publish article on English. But if you
have questions now
- we are ready for discussion.
If some of English-speaking comrades of ReactOS would like to work
with errors list,
generated with PVS-Studio we have prepared for them translation of
errors explanations, here it is:
http://www.viva64.com/external-pictures/txt/PVS-Studio-vs-ReactOS-en-unicod…
".
Original article refers to long list of generated errors with manually
added explanations for errors
found by their static checker, so this is translated version of that list.
---
Looking backward to few applied patches, it turns out that not all of
them were absolutely useful,
some patches were reversed, etc. But nevertheless, I think it makes
sense to use this tool. They
promised to donate some version of PVS-Studio to project, and it is to
ROS developers to decide is it worth of taking.
What I would suggest: anybody working with some module or part of code
can take corresponding part
of messages (or in future, possibly check with tool only these parts
of interest) and work with them.
Also Karpov gave good advise to check newly written code, since it is
still of interest to developer:
write and time for time test with it.
P.S. Disclaimer: I am not in any connection with "SiProVer"
Regards,
M.A.
Nice work guys.
It was great to watch you pull this together as a team.
Hopefully there's more to come :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of akhaldi(a)svn.reactos.org
Sent: 09 September 2011 11:55
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [akhaldi] 53653: [SHELL32] * Reintegrate the c++ shell32 branch. Exemplary team-work.. kudos ! * Better code quality, more tests run with less failures... and more. * Dedicated to everyone who help...
Author: akhaldi
Date: Fri Sep 9 10:55:09 2011
New Revision: 53653
URL: http://svn.reactos.org/svn/reactos?rev=53653&view=rev
Log:
[SHELL32]
* Reintegrate the c++ shell32 branch. Exemplary team-work.. kudos !
* Better code quality, more tests run with less failures... and more.
* Dedicated to everyone who helped ;)
Le 23/08/2011 10:58, tkreuzer(a)svn.reactos.org a écrit :
> Author: tkreuzer
> Date: Tue Aug 23 08:58:15 2011
> New Revision: 53399
>
> URL: http://svn.reactos.org/svn/reactos?rev=53399&view=rev
> Log:
> [VMWINST] Fix amd64 build
>
What about :
[VMWINST] Get rid of this useless relic.
I mean it's something we have to maintain, it was written for
antediluvian vmware versions, and I see no reason to have such a thing.
I may as well write an application to install specific ATI card drivers,
or intel chipset drivers...
Hello Claudiu!
I notice some weird tab/spaces modifications here.
Regards.
Jérôme.
Le 03/09/2011 16:20, cmihail(a)svn.reactos.org a écrit :
> Author: cmihail
> Date: Sat Sep 3 14:20:03 2011
> New Revision: 53543
>
> URL: http://svn.reactos.org/svn/reactos?rev=53543&view=rev
> Log:
> [shell32.dll]
> - Fix bug related to correct error code returning in delete_files. The value of 1026 was revealed to be returned by windows 2003 server. Score several passed winetests.
> - Fix a bug in ShellLink::SetShowCmd and score one more passed winetest
>
> Modified:
> branches/shell32_new-bringup/dll/win32/shell32/shelllink.cpp
> branches/shell32_new-bringup/dll/win32/shell32/shlfileop.cpp
>
>
Am 03.09.2011 02:08, schrieb cmihail(a)svn.reactos.org:
> Author: cmihail
> Date: Sat Sep 3 00:08:11 2011
> New Revision: 53537
>
> URL:http://svn.reactos.org/svn/reactos?rev=53537&view=rev
> Log:
> [shell32.dll]
> [FORMATTING]
> - Format the code to a more acceptable level. This is just for my sanity while sifting through it.
> /* skip the remaining spaces */
> - while (*cs==0x0009 || *cs==0x0020) {
> + while (*cs==0x0009 || *cs==0x0020)
> + {
> cs++;
> }
> if (*cs==0)
>
Please don't mix tabs and spaces or we'll end up looking like GNU style ;-)
Since the file already uses spaces (as we use almost everywhere), please
stick to that here.
Regards,
Timo
Hey again,
On 2011-09-01 15:18, dchapyshev(a)svn.reactos.org wrote:
> --- trunk/reactos/dll/win32/netshell/lanstatusui.c [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/netshell/lanstatusui.c [iso-8859-1] Thu Sep 1 13:18:22 2011
> @@ -179,7 +179,7 @@
> pContext->Status = 3;
> }
> }
> - else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE || MIB_IF_OPER_STATUS_DISCONNECTED)
> + else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE | MIB_IF_OPER_STATUS_DISCONNECTED)
> {
> if (pContext->Status != 4)
> {
>
this should more likely be
else if (IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_UNREACHABLE ||
IfEntry.dwOperStatus == MIB_IF_OPER_STATUS_DISCONNECTED)
Some nice fixes right there by the way. :)
*hopes this might fix some evil bugs that have been lurking* ;)
Thanks,
Tom
Funny how Windows works without these hacks.
Let's hide more bugs :D
Best regards,
Alex Ionescu
On Tue, Aug 30, 2011 at 12:01 PM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Tue Aug 30 12:01:01 2011
> New Revision: 53496
>
> URL: http://svn.reactos.org/svn/reactos?rev=53496&view=rev
> Log:
> [HAL]
> We cannot make any assumptions about the latency whith which the timer
> interrupt fires after a rollover, since VBox (other VMs probably as well)
> doesn't always meet this. Add another check to KeQueryPerformanceCounter
> that gracefully handles missing interrupts. Also raise to DISPATCH_LEVEL,
> since the function is not reentrant.
>
> Modified:
> trunk/reactos/hal/halx86/generic/timer.c
>
> Modified: trunk/reactos/hal/halx86/generic/timer.c
> URL:
> http://svn.reactos.org/svn/reactos/trunk/reactos/hal/halx86/generic/timer.c…
>
> ==============================================================================
> --- trunk/reactos/hal/halx86/generic/timer.c [iso-8859-1] (original)
> +++ trunk/reactos/hal/halx86/generic/timer.c [iso-8859-1] Tue Aug 30
> 12:01:01 2011
> @@ -253,6 +253,7 @@
> {
> LARGE_INTEGER CurrentPerfCounter;
> ULONG CounterValue, ClockDelta;
> + KIRQL OldIrql;
>
> /* If caller wants performance frequency, return hardcoded value */
> if (PerformanceFrequency) PerformanceFrequency->QuadPart =
> PIT_FREQUENCY;
> @@ -262,6 +263,10 @@
>
> /* Check if interrupts are disabled */
> if(!(__readeflags() & EFLAGS_INTERRUPT_MASK)) return HalpPerfCounter;
> +
> + /* Raise irql to DISPATCH_LEVEL */
> + OldIrql = KeGetCurrentIrql();
> + if (OldIrql < DISPATCH_LEVEL) KfRaiseIrql(DISPATCH_LEVEL);
>
> do
> {
> @@ -287,13 +292,21 @@
> /* Add the clock delta */
> CurrentPerfCounter.QuadPart += ClockDelta;
>
> - /* This must be true unless HalpPerfCounter has changed sign,
> - which takes approximately 245,118 years */
> - ASSERT(CurrentPerfCounter.QuadPart >= HalpLastPerfCounter.QuadPart);
> + /* Check if the value is smaller then before, this means, we somehow
> + missed an interrupt. This is a sign that the timer interrupt
> + is very inaccurate. Probably a virtual machine. */
> + if (CurrentPerfCounter.QuadPart < HalpLastPerfCounter.QuadPart)
> + {
> + /* We missed an interrupt. Assume we will receive it later */
> + CurrentPerfCounter.QuadPart += HalpCurrentRollOver;
> + }
>
> /* Update the last counter value */
> HalpLastPerfCounter = CurrentPerfCounter;
>
> + /* Restore previous irql */
> + if (OldIrql < DISPATCH_LEVEL) KfLowerIrql(OldIrql);
> +
> /* Return the result */
> return CurrentPerfCounter;
> }
>
>
>
Hi,
I am the maintainer of uranos (http://uranos.sf.net) and want to
implement the unattended setup of ReactOS into uranos. I read that you
have implemented a answer file into ReactOS.
Because of uranos does all the parts which is done by the txtinstaller
from ReactOS (partition disk, write mbr, copy files and so on) from a
linux boot environment - I want to know if it is possible to place the
unattended.inf into the filesystem so the ReactOS is read the file in
the first GUI boot.
Thank you! Cheers mario
I want to do some testing on physical machines until now was doing the
vbox will charge the machine a good desepenho
memory and I'll need to spend sitema ospedeiro vbox and the problem
and that the machines do not have a serial port
was taking a look at these wiki but did not see exact references on
how to get the debug log on the cable network
vbox but works well for the network that will be with you
http://www.reactos.org/wiki/Debugginghttp://www.reactos.org/wiki/ReactOS_Remote_Debugger#TCP.2FIP_.28QEMU_only.29