Hi All,
Some of you might have seen my recent on the post regarding the build
process:
http://www.reactos.org/forum/viewtopic.php?f=9&t=12240&start=15
As I mentioned, it would help greatly to lower the barrier-to-entry to
less-experienced developers, as well as more experienced developers who
might have limited time budgets [Who among us does not have a limited time
budget?].
I wanted to send out this message to let everyone know that I intend to use
what bit of time that I available right now, at the beginning of January, to
tackle this issue head-on. Again, my purpose here is not to step on anyone's
toes, but make certain that we never turn away a potentially-valuable
contributor simply because they are unnecessarily removed from their
development comfort zone. I do realize that there is already on-going work
on the build process, and I have no intention of interfering with that.
I will wait 24-hours for any objections/reservations from now before making
a hard commitment, but frankly, we really to get this done, like right now.
Happy New Year. :)
-JC
Hi All,
I wanted to start fresh since there are several emails/chats going around
regarding Visual Studio builds of ReactOS.
First, I would like to state something clearly, since there seems to be
implicit thoughts to the contrary:
Visual Studio is capable of handling a project the size of ReactOS in its
entirety in one .sln without any major performance problems, if it is
configured correctly.
The key phrase is "if it is configured correctly".
For example:
1. The performance problem during loading occurs because IntelliSense
is being unnecessarily taxed (quite heavily in fact). This is fixed by
adding #define WIN32_LEAN_AND_MEAN as appropriate to the IDE settings.
2. The lack of x86_64 and ARM support is occurring because there is a
lack of x86_64 and ARM support. :D
3. Some people might look at the Solution Workspace window, see 800
projects, and think, "Wow. That's a lot of projects. I will be scrolling all
day long." There is a solution (no pun intended) for that: Don't put 800
projects linearly in the Solution Workspace. Put them in a hierarchy that
matches, exactly, the hierarchy of the ReactOS project.
4. That build paths will be broken if the user decides to move his/her
ReactOS hierarchy to a different directory after the .sln and .vcxproj files
have been generated by cmake, is easily fixed: Use relative paths in the IDE
project settings instead.
5. The fact that it is not possible to build, say, just applications,
or just drivers, without hunting-and-pecking projects in the Solution
Workspace, is related to problem #3: The projects are not yet placed into a
hierarchy that mirrors the ReactOS repository. If the projects were placed
into a hierarchy that mirrors the ReactOS repository, it would be possible
to select, say, drivers, right-click, select Build, and all the drivers will
be built depends on what was done in the code, as well as setting proper
paths in the IDE. The use would be able to toggle between Debug/Release,
x86_32/ARM, and perform the same operation, with expected results.
I could go on, but you get the point. It is trivial to set up Visual Studio
so that it "behaves properly". I started this effort, and was 10% into the
800 projects, at least setting up the structure, for x86_32, x86_64, and
ARM; but I throttled-back because I do not like redundancy of effort, and
Amine was already well on his way doing something that was essentially
similar. I am confident that, over time, he will solve these problems.
In the meantime, I would hope that we keep in mind that the problem is not
the tool. The problem is that the tool has not been given a chance to be
configured properly.
If we configure it properly, these problems go away, and most importantly,
when a new developer comes and sees ReactOS in Visual Studio for the first
time, what they see makes sense. Let me repeat that: The measure of success
here, is not whether it is possible to get Visual Studio to compile ReactOS,
although I read some writings about how some wanted the Microsoft compiler
over GCC. The measure of success is whether a heavily experience user of
Visual Studio sees the IDE for the first time with ReactOS in it, and not
start mumbling things like.."Ok.uh... why did they do that.???"
By contrast we want them to say:
"Wow.800-project solution. Let's see, x86_32, x86_64, ARM support..nice.both
Debug and Release present.good good.looks like Solution Workspace mirrors
what is on disk..cool.#include paths in IDE project settings are relative to
root of solution so I can move solution to another disk if I like.appreciate
that.IntelliSense seems to be working correctly.and this livecd thing.I
guess right-clicking on that and doing Build does minimum operations
necessary to generate a live CD. I wonder what happens when I try to execute
the livecd project after built. Wow.that is too awesome!!! Ok. Everything
makes sense. I can handle myself from here. Thanks."
IMO, we should give Amine time to get the ReactOS repository into this
state.. I am re-attaching an image I sent last week about what I would have
done for the structure of the Solution Workspace. As you can see from this
structure, there is nothing intimidating or inefficient about this
structure, and it mirrors what ReactOS veterans see on disk every day.
Cheers.
-John
cid:image001.png@01CDEA11.FFD64AF0
I see a problem with this change.
A debug breakpoint will always break into the debugger exactly where it
is. Like an ASSERT does.
But an exception will usually end up in the installed exception handler.
This does not really help with figuring out what went wrong.
Am 07.01.2013 00:29, schrieb hbelusca(a)svn.reactos.org:
> Author: hbelusca
> Date: Sun Jan 6 23:29:05 2013
> New Revision: 58135
>
> URL: http://svn.reactos.org/svn/reactos?rev=58135&view=rev
> Log:
> [REACTOS]
> - Fix the debugging macros I've introduced in r58132; in particular do not use while(true); for forbidding the user to continue execution, but instead raise an exception with EXCEPTION_NONCONTINUABLE flag (included when called RtlRaiseStatus).
> - Adjust the definition of RtlRaiseStatus (in kernel-mode it is ExRaiseStatus which is used).
>
> Modified:
> trunk/reactos/include/reactos/debug.h
>
> Modified: trunk/reactos/include/reactos/debug.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/debug.h?re…
> ==============================================================================
> --- trunk/reactos/include/reactos/debug.h [iso-8859-1] (original)
> +++ trunk/reactos/include/reactos/debug.h [iso-8859-1] Sun Jan 6 23:29:05 2013
> @@ -15,7 +15,7 @@
> #ifndef __INTERNAL_DEBUG
> #define __INTERNAL_DEBUG
>
> -/* Define DbgPrint/DbgPrintEx/RtlAssert unless the NDK is used */
> +/* Define DbgPrint/DbgPrintEx/RtlAssert/RtlRaiseStatus unless the NDK is used */
> #if !defined(_RTLFUNCS_H) && !defined(_NTDDK_)
>
> /* Make sure we have basic types (some people include us *before* SDK)... */
> @@ -51,7 +51,27 @@
> PCHAR Message
> );
>
> +#ifndef _NTDEF_ /* Guard against redefinition from ntdef.h */
> + typedef _Return_type_success_(return >= 0) LONG NTSTATUS;
> +#endif
> +__analysis_noreturn
> +NTSYSAPI
> +VOID
> +NTAPI
> +RtlRaiseStatus(
> + _In_ NTSTATUS Status
> +);
> +
> #endif /* !defined(_RTLFUNCS_H) && !defined(_NTDDK_) */
> +
> +
> +/* Fix usage of RtlRaiseStatus */
> +#if !defined(_RTLFUNCS_H) && defined(_NTDDK_)
> + #define RaiseStatus ExRaiseStatus
> +#else
> + #define RaiseStatus RtlRaiseStatus
> +#endif /* !defined(_RTLFUNCS_H) && defined(_NTDDK_) */
> +
>
> #ifndef assert
> #ifndef NASSERT
> @@ -136,11 +156,7 @@
>
> #endif /* not DBG */
>
> -/*
> - * These macros are designed to display an optional printf-like
> - * user-defined message and to break into the debugger.
> - * After that they allow to continue the program execution.
> - */
> +/******************************************************************************/
> /* For internal purposes only */
> #define __ERROR_DBGBREAK(...) \
> do { \
> @@ -148,6 +164,18 @@
> DbgBreakPoint(); \
> } while (0)
>
> +/* For internal purposes only */
> +#define __ERROR_FATAL(Status, ...) \
> +do { \
> + DbgPrint("" __VA_ARGS__); \
> + RaiseStatus((Status)); \
> +} while (0)
> +
> +/*
> + * These macros are designed to display an optional printf-like
> + * user-defined message and to break into the debugger.
> + * After that they allow to continue the program execution.
> + */
> #define ERROR_DBGBREAK(...) \
> do { \
> __NOTICE(ERROR, "\n"); \
> @@ -165,19 +193,18 @@
> * user-defined message and to break into the debugger.
> * After that they halt the execution of the current thread.
> */
> -#define ERROR_FATAL(...) \
> -do { \
> - __NOTICE(UNRECOVERABLE ERROR, "\n"); \
> - __ERROR_DBGBREAK(__VA_ARGS__); \
> - while (TRUE); \
> +#define ERROR_FATAL(...) \
> +do { \
> + __NOTICE(UNRECOVERABLE ERROR, "\n"); \
> + __ERROR_FATAL(STATUS_ASSERTION_FAILURE, __VA_ARGS__); \
> } while (0)
>
> #define UNIMPLEMENTED_FATAL(...) \
> do { \
> __NOTICE(UNRECOVERABLE ERROR, "is UNIMPLEMENTED!\n"); \
> - __ERROR_DBGBREAK(__VA_ARGS__); \
> - while (TRUE); \
> -} while (0)
> + __ERROR_FATAL(STATUS_NOT_IMPLEMENTED, __VA_ARGS__); \
> +} while (0)
> +/******************************************************************************/
>
> #define ASSERT_IRQL_LESS_OR_EQUAL(x) ASSERT(KeGetCurrentIrql()<=(x))
> #define ASSERT_IRQL_EQUAL(x) ASSERT(KeGetCurrentIrql()==(x))
>
>
>
With all respect, I don't understand many of these changes. Answering
between the lines.
On 04.01.2013 15:47, hbelusca(a)svn.reactos.org wrote:
> NTSTATUS
> @@ -643,7 +643,8 @@
> /* FIXME: TODO */
> DPRINT1("You have implemented the KD routines for searching PCI debugger"
> "devices, but you have forgotten to implement this routine\n");
> - while (TRUE);
> + UNIMPLEMENTED;
> + ASSERT(FALSE); // while (TRUE);
> }
It already prints a mandatory log message that this part is
unimplemented. And execution is supposed to stop after printing this
message, because it's meaningless to continue (that's why while(TRUE);
was put there in the first place).
>
> static ULONG NTAPI
> @@ -678,7 +679,7 @@
> {
> /* /PCILOCK is not yet supported */
> UNIMPLEMENTED;
> - while (TRUE);
> + ASSERT(FALSE); // while (TRUE);
> }
> #endif
> /* Now create the correct resource list based on the supported bus ranges */
It already has UNIMPLEMENTED; and now you added an ASSERT(FALSE); which
essentially is the same thing. And if continuation is possible, then
just UNIMPLEMENTED would be enough.
I'd like some general solution to this. Like, UNIMPLEMENTED_FATAL() or
something like that.
Any thoughts?
Regards,
Aleksey Bragin
Hello!
Due to Christmas and New Year holidays this month's status meeting makes
little sense. Preliminary it's rescheduled to January, exact dates will
be proposed after speaking to our team members.
Thank you all for your work in 2012, and bright future awaits us in
2013, I'm sure.
Best regards,
Aleksey Bragin
Hi,
due to a server move, one IPv6 link is currently down waiting for its replacing link (and for DNS update). Affected services are mainly Jira, Fisheye & Drupal website.
We are working on it. Sorry for the inconvenience.
IPv4 is all fine on those servers.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
I think that in the spec files semantics, destination strings are just
buffers and should be considered as pointers.
hbelusca(a)svn.reactos.org a écrit :
> Author: hbelusca
> Date: Wed Dec 26 19:26:08 2012
> New Revision: 58016
>
> URL: http://svn.reactos.org/svn/reactos?rev=58016&view=rev
> Log:
> [MSVCRT]
> Export __crtLCMapStringW and correct __crtLCMapStringA: their prototypes are :
>
> int CDECL __crtLCMapStringW(LCID lcid, DWORD mapflags, const wchar_t *src,
> int srclen, wchar_t *dst, int dstlen, unsigned int codepage, int xflag)
>
> and
>
> int CDECL __crtLCMapStringA(LCID lcid, DWORD mapflags, const char* src,
> int srclen, char* dst, int dstlen, unsigned int codepage, int xflag)
>
> Needed by SVN.
>
> Modified:
> trunk/reactos/dll/win32/msvcrt/msvcrt.spec
>
> Modified: trunk/reactos/dll/win32/msvcrt/msvcrt.spec
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/dll/win32/msvcrt/msvcrt.sp…
> ==============================================================================
> --- trunk/reactos/dll/win32/msvcrt/msvcrt.spec [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/msvcrt/msvcrt.spec [iso-8859-1] Wed Dec 26 19:26:08 2012
> @@ -143,8 +143,8 @@
> @ cdecl __crtCompareStringW(long long wstr long wstr long) kernel32.CompareStringW
> @ cdecl __crtGetLocaleInfoW(long long ptr long) kernel32.GetLocaleInfoW
> @ cdecl __crtGetStringTypeW(long long wstr long ptr)
> -@ cdecl __crtLCMapStringA(long long str long ptr long long long)
> -# stub __crtLCMapStringW
> +@ cdecl __crtLCMapStringA(long long str long str long long long)
> +@ cdecl __crtLCMapStringW(long long wstr long wstr long long long)
> @ cdecl __daylight() __p__daylight
> @ cdecl __dllonexit(ptr ptr ptr)
> @ cdecl __doserrno()
>
>
Hello,
starting now a new debug testbot slave is available. It is running VMware Player 5.0.1 under Linux x64.
It will run all the ISOs built by the Linux builder.
Its results are available at the usual place: http://www.reactos.org/testman with the name: CMake_x86_GCCLin (VMPlayer).
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Hello and Merry Christmas!
I know there are people from various technical universities around the
world subscribed to this list.
If you work there, please reply to me, as I'm looking for some
collaboration related to Operating Systems theory course and ReactOS.
Thank you,
Aleksey Bragin
P.S. Crossposting to both ros-dev and ros-general is a bad idea, but I'm
doing this to reach out all our subscribers. Sorry for inconvinience.
Are you planning on resurrecting this branch Thomas?
On 23/12/2012 10:25, "tfaber(a)svn.reactos.org" <tfaber(a)svn.reactos.org>
wrote:
>Author: tfaber
>Date: Sun Dec 23 10:25:19 2012
>New Revision: 57976
>
>URL: http://svn.reactos.org/svn/reactos?rev=57976&view=rev
>Log:
>[EXPLORER_NEW]
>- Add a manifest file to support theming
>- Formatting fixes
>- Based on Andrew Green's GSoC branch
>
>Added:
> trunk/reactos/base/shell/explorer-new/explorer.exe.manifest (with
>props)
>Modified:
> trunk/reactos/base/shell/explorer-new/explorer.rc
> trunk/reactos/base/shell/explorer-new/taskswnd.c
> trunk/reactos/base/shell/explorer-new/trayntfy.c
Fixed as well.
Forgot that one, sorry.
Le samedi 15 décembre 2012 à 12:48 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Release while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Release/builds/289
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1B
>
> Build Reason: The Periodic scheduler named 'release' triggered this build
> Build Source Stamp: HEAD
> Blamelist:
>
> BUILD FAILED: failed compile_1
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Fixed.
The needed env variable is now exported.
Le vendredi 14 décembre 2012 à 21:56 +0000, buildbot(a)reactos.org a
écrit :
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/2066
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 57913
> Blamelist: akhaldi
>
> BUILD FAILED: failed compile_1
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
YAY!
Finally this is fixed!
Am 07.12.2012 19:00, schrieb tfaber(a)svn.reactos.org:
> Author: tfaber
> Date: Fri Dec 7 18:00:30 2012
> New Revision: 57815
>
> URL: http://svn.reactos.org/svn/reactos?rev=57815&view=rev
> Log:
> [SPIDER]
> - Only dissolve a stack of cards if they're of the same color
> - Allow easier recognition of suit in concealed cards
> - Patch by Marcel Leyendeckers, m dot leyendeckers at gmx dot de
> CORE-6808 #resolve #comment Committed. Thanks!
>
> Modified:
> trunk/reactos/base/applications/games/spider/spigame.cpp
>
> Modified: trunk/reactos/base/applications/games/spider/spigame.cpp
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/base/applications/games/sp…
> ==============================================================================
> --- trunk/reactos/base/applications/games/spider/spigame.cpp [iso-8859-1] (original)
> +++ trunk/reactos/base/applications/games/spider/spigame.cpp [iso-8859-1] Fri Dec 7 18:00:30 2012
> @@ -249,7 +249,8 @@
> int i, max = NUM_ONECOLOR_CARDS - dragcards.NumCards() - 1;
>
> /* Dragged cards have been checked to be in order, check stack cards */
> - if (stackLookingGood(mystack, max))
> + if (mystack[0].Suit() == dragcard.Suit() &&
> + stackLookingGood(mystack, max))
> {
> CardStack s = stackobj.GetCardStack();
> CardStack f;
> @@ -279,8 +280,8 @@
> {
> int i, pos;
>
> - /* Compute the value for yRowStackCardOffset based on the height of the card, so the card number isn't hidden on larger cards */
> - yRowStackCardOffset = (int)(__cardheight / 6.7);
> + /* Compute the value for yRowStackCardOffset based on the height of the card, so the card number and suite isn't hidden on larger cards except Ace */
> + yRowStackCardOffset = (int)(__cardheight / 6.4);
>
> pDeck = SpiderWnd.CreateRegion(0, true, 0, 0, -15, 0);
> pDeck->SetFaceDirection(CS_FACE_DOWN, 0);
>
>
>
On 04.12.2012 2:15, pschweitzer(a)svn.reactos.org wrote:
> - ExFreePool(SharedRange);
> + ExFreePoolWithTag(SharedRange, 'FSRA');
> /* We need to rebuild the list of shared ranges. */
> DPRINT("Removing the lock entry %wZ (%08x%08x:%08x%08x)\n",
> &FileObject->FileName,
> @@ -1287,7 +1287,7 @@
> SharedRange = CONTAINING_RECORD(SharedEntry, LOCK_SHARED_RANGE, Entry);
> SharedEntry = SharedEntry->Flink;
> RemoveEntryList(SharedEntry);
> - ExFreePool(SharedRange);
> + ExFreePoolWithTag(SharedRange, 'FSRA');
> }
> while ((Entry = RtlGetElementGenericTable(&InternalInfo->RangeTable, 0)) != NULL)
> {
>
>
It would be a good idea to add this to TAG_ list of defines.
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 29th of November, 19:00 UTC.
The meeting will be at irc://dev.reactos.org (Port 6667, no SSL) in the
channel #meeting, or as Pierre/Colin say. Note that the IRC service will
only be started shortly before the meeting. Your participation passwords
will be emailed to you shortly before the meeting starts, and they are
going to be different once again as they are not stored in any database.
Hopefully it's not much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
The agenda will be posted shortly before the meeting, suggestions are
welcome (send them to my email as usual). Hot topics would include
progress made during this month, contracts updates, release plans (if
any), web site progress (if any).
With the best regards,
Aleksey Bragin
Hi all,
Pierre Schweitzer <pierre(a)reactos.org> wrote:
> due to a hardware migration ongoing on one of our hypervisors, the
> following services are currently down:
The server upgrade went successfully and everything is back to normal now.
Cheers,
Colin
Hi all,
Several ReactOS services will be moved to a new server next Friday. As
this migration highly depends on our hosting provider, the downtime may
be up to 24 hours.
Affected services include:
- ns1.reactos.org
- playground.reactos.org
- jira.reactos.org
The upgrade will improve reliability and adds resources for additional
services in the future.
Of course, you will be informed once the migration is over.
Cheers,
Colin
Would you mind not "cleaning up formatting" by going against our coding
style and doing the very thing I even taught you not to do during your
initial patches/code reviews?
Thanks.
Best regards,
Alex Ionescu
On Tue, Nov 13, 2012 at 1:08 PM, <hbelusca(a)svn.reactos.org> wrote:
> - if ((ServerDll) && (ServerDll->HardErrorCallback))
> + if (ServerDll && ServerDll->HardErrorCallback)
>
We have 90 % C. So disabling OPTIMIZE_OUTPUT_FOR_C will probably result
in worse readable output for 90% of the code.
Am 05.11.2012 12:14, schrieb pschweitzer(a)svn.reactos.org:
> Author: pschweitzer
> Date: Mon Nov 5 11:13:59 2012
> New Revision: 57674
>
> URL: http://svn.reactos.org/svn/reactos?rev=57674&view=rev
> Log:
> [DOXYGEN]
> ReactOS is not C only.
> Enable support builtin STL.
>
> Modified:
> trunk/reactos/Doxyfile
>
> Modified: trunk/reactos/Doxyfile
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/Doxyfile?rev=57674&r1=5767…
> ==============================================================================
> --- trunk/reactos/Doxyfile [iso-8859-1] (original)
> +++ trunk/reactos/Doxyfile [iso-8859-1] Mon Nov 5 11:13:59 2012
> @@ -196,7 +196,7 @@
> # For instance, some of the names that are used will be different. The list
> # of all members will be omitted, etc.
>
> -OPTIMIZE_OUTPUT_FOR_C = YES
> +OPTIMIZE_OUTPUT_FOR_C = NO
>
> # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
> # sources only. Doxygen will then generate output that is more tailored for
> @@ -236,7 +236,7 @@
> # func(std::string) {}). This also make the inheritance and collaboration
> # diagrams that involve STL classes more complete and accurate.
>
> -BUILTIN_STL_SUPPORT = NO
> +BUILTIN_STL_SUPPORT = YES
>
> # If you use Microsoft's C++/CLI language, you should set this option to YES to
> # enable parsing support.
>
>
>
Hello,
the meeting is rescheduled to 1st of November, as I don't see a point to
do a meeting if zwabbit, caemyr and other can not attend. 1st of
November will also be thursday, just one week late.
Sorry for inconvenience.
And it's time for agenda proposals already, please send them in to my
email address as usual. Thanks.
Best regards,
Aleksey Bragin.
Eric, with my rewrite, you can call RtlEqualPrefixSid instead of using
LsapIsPrefixSid.
The code should be the same
Best regards,
Alex Ionescu
On Sun, Oct 7, 2012 at 7:33 PM, <ekohl(a)svn.reactos.org> wrote:
> LsapIsPrefixSid
Hiya
Unfortunately, my lappy has died yesterday. I`ll RMA it this week (its
just 6mo old...) but who knows how long will it take. I`ll get one as
replacement from my work tomorow, but still this means no testing for
me, just the web works for few next weeks.
--
With best regards
Caemyr
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 28th of September, 19:00 UTC.
The meeting will be at irc://dev.reactos.org (Port 6667, no SSL) in the
channel #meeting, or as Pierre/Colin say. Note that the IRC service will
only be started shortly before the meeting. Your participation passwords
will be emailed to you shortly before the meeting starts, and they are
going to be different once again as they are not stored in any database.
Hopefully it's not much of inconvenience.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. As usual, Z98 is welcome to volunteer.
The agenda will be posted shortly before the meeting, suggestions are
welcome (send them to my email as usual).
With the best regards,
Aleksey Bragin.
@Giannis - as you required:
http://svn.reactos.org/svn/reactos?view=revision&revision=57330
This commit is causing the following crash in user32_apitest:desktop
(reported in CORE-6682
desktop.c:83: Test failed: 3: expected error 0xc0000142 in child process
got 0x0
(../../win32ss/user/ntuser/desktop.c:340) err: Failed to reference
desktop WinSta0/Default PID: --!
(../../win32ss/user/ntuser/main.c:333) err: Failed to assign default
dekstop and winsta to process
(../../win32ss/user/ntuser/main.c:374) err: UserCreateThreadInfo failed!
Freeing pti 0xB09C5A70 for TID 00000590
(../../dll/ntdll/ldr/ldrinit.c:829) LDR: DLL_PROCESS_ATTACH for dll
"user32.dll" (InitRoutine: 77ABADBF) failed
(../../dll/ntdll/ldr/ldrinit.c:2111) LDR: LdrpProcessInitialization
failed running initialization routines; status c0000142
(../../dll/ntdll/ldr/ldrinit.c:2140) LDR: Process initialization failure
for C:\ReactOS\bin\user32_apitest.exe; NTSTATUS = c0000142
(../../subsystems/win32/csrss/csrsrv/api/wapi.c:1221) Exception in
59c.590. Killing...
(../../win32ss/user/ntuser/desktop.c:340) err: Failed to reference
desktop NonExistantDesktop PID: --!
(../../win32ss/user/ntuser/main.c:333) err: Failed to assign default
dekstop and winsta to process
(../../win32ss/user/ntuser/main.c:374) err: UserCreateThreadInfo failed!
Freeing pti 0xB097F008 for TID 00000588
(../../dll/ntdll/ldr/ldrinit.c:829) LDR: DLL_PROCESS_ATTACH for dll
"user32.dll" (InitRoutine: 77ABADBF) failed
(../../dll/ntdll/ldr/ldrinit.c:2111) LDR: LdrpProcessInitialization
failed running initialization routines; status c0000142
(../../dll/ntdll/ldr/ldrinit.c:2140) LDR: Process initialization failure
for C:\ReactOS\bin\user32_apitest.exe; NTSTATUS = c0000142
(../../subsystems/win32/csrss/csrsrv/api/wapi.c:1221) Exception in
594.588. Killing...
(../../win32ss/user/ntuser/desktop.c:308) err: Failed to reference
window station \Windows\WindowStations\NonExistantWinsta PID: --!
(../../win32ss/user/ntuser/main.c:333) err: Failed to assign default
dekstop and winsta to process
(../../win32ss/user/ntuser/main.c:374) err: UserCreateThreadInfo failed!
Freeing pti 0xB0A444F8 for TID 00000580
(../../dll/ntdll/ldr/ldrinit.c:829) LDR: DLL_PROCESS_ATTACH for dll
"user32.dll" (InitRoutine: 77ABADBF) failed
(../../dll/ntdll/ldr/ldrinit.c:2111) LDR: LdrpProcessInitialization
failed running initialization routines; status c0000142
(../../dll/ntdll/ldr/ldrinit.c:2140) LDR: Process initialization failure
for C:\ReactOS\bin\user32_apitest.exe; NTSTATUS = c0000142
(../../subsystems/win32/csrss/csrsrv/api/wapi.c:1221) Exception in
58c.580. Killing...
(../../ntoskrnl/mm/ARM3/section.c:386) Out of system view space
Assertion 'Base' failed at ../../ntoskrnl/mm/ARM3/section.c line 1041
[7h
Entered debugger on embedded INT3 at 0x0008:0x8092582e.
kdb:> bt
Eip:
<NTOSKRNL.EXE:12582f (../../lib/rtl/i386/debug_asm.S:35
(_DbgBreakPoint@0))>
Frames:
<NTOSKRNL.EXE:b773f (../../ntoskrnl/mm/ARM3/section.c:1041
(MiMapViewInSystemSpace@16))>
<NTOSKRNL.EXE:b78ee (../../ntoskrnl/mm/ARM3/section.c:2655
(MmMapViewInSessionSpace@12))>
<win32k.sys:148c8 (../../win32ss/user/ntuser/misc/usrheap.c:201
(UserCreateHeap))>
<win32k.sys:359e1 (../../include/ddk/wdm.h:0 (UserDestroyThreadInfo@4))>
<NTOSKRNL.EXE:11100e (../../ntoskrnl/ke/i386/traphdlr.c:1629
(@KiFastCallEntryHandler@8))>
<NTOSKRNL.EXE:10ebfd (../../ntoskrnl/ke/i386/trap.s:150
(_KiFastCallEntry))>
<ntdll.dll:b065>
<user32_apitest.exe:84f2>
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
Date: Wed, 19 Sep 2012 02:32:21 +0000
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/6627
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: 57330
Blamelist: ion
BUILD FAILED: failed Cleanup
sincerely,
-The Buildbot
--
With best regards
Caemyr
Dear ReactOS developers,
I follow ReactOS development for some years.
I have successfully tested and reported our uLAN driver
with PCI cards on ReactOS two years ago.
The latest inclusion of USB VENDOR device requests
in ReactOS allowed to finally run driver with our real
USB hardware with QEMU KVM USB device pass-through
setup.
ReactOS tuned version of the uLAN driver installs
and is fully functional when tested from CHROMuLAN application.
But there are more issues still and I would be happy
if somebody can help with these or give me hint about
possible incompatibility in our driver.
The tests were conducted against ReactOS 57254 build.
uLAN driver is from GIT source repository
http://ulan.sourceforge.net/http://ulan.git.sourceforge.net/git/gitweb.cgi?p=ulan/ulan-drv;a=tree;f=ul_…
uLAN driver was build by MS WDF VC version 15.00.30729.207
The issues:
1) the first minor one - ReactOS requires minimal transfer size for
URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE/USB_CONFIGURATION_DESCRIPTOR_TYPE function
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbhub/pdo.c:244) URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE
ulan: _usb_submit_urb : return from IoCallDriver USBD 103
ulan: _usb_submit_urb : URB status = 0 status = 0 irp status 0
uLan: _usb_submit_urb done with status:0x0
uLan: _usb_get_descriptor done with status:0x0
uLan: usb_device_descriptor done with status:0x0
uLan: usb_get_configuration
uLan: _usb_get_descriptor (type=0x2,idx=0x0)
ulan: _usb_submit_urb : enter
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbhub/pdo.c:244) URB_FUNCTION_GET_DESCRIPTOR_FROM_DEVICE
Assertion 'Urb->UrbControlDescriptorRequest.TransferBufferLength >= sizeof(USB_CONFIGURATION_DESCRIPTOR)' failed at /srv/buildbot_
cmake/full_cmake/build/lib/drivers/libusb/hub_controller.cpp line 1560
Entered debugger on embedded INT3 at 0x0008:0x80924c3a.
Unmodified uLAN driver asks for the first four bytes descriptor bytes firest
and after obtaining size of the whole descriptor it prepares full size transfer.
ReactOS asserts for this shorted 4 bytes transfer. I have adapted driver
to use sizeof(USB_CONFIGURATION_DESCRIPTOR) size for initial probe transfer
in USB_CONFIGURATION_DESCRIPTOR_TYPE case. This makes ReactOS happy,
but I would like to know which side should be updated in the future.
Is there defined in some spec that initial probe for size has to be at least
of sizeof(USB_CONFIGURATION_DESCRIPTOR) or the ReactOS is more strict than
necessary and assert should be modified to allow truncated probes or at least
4 bytes ones in addition?
The full log at
http://cmp.felk.cvut.cz/~pisa/ulan/reactos/reactos-ul-win-confdesc.log
2) Driver can be enabled and disabled at runtime but shutdown does not finish,
is blocked somehow but system/cursor is responsive
http://cmp.felk.cvut.cz/~pisa/ulan/reactos/reactos-ul-enabled-at-runtime.log
I have no idea what is the problem. Driver works correctly on Windows from 2k to Win7
and latest version supports even suspend and resume on all these platforms.
3) When driver and device are installed/present from boot time, boot hangs
http://cmp.felk.cvut.cz/~pisa/ulan/reactos/reactos-ul-during-boot.log
(/srv/buildbot_cmake/full_cmake/build/lib/drivers/libusb/hub_controller.cpp:313) [USBLIB] SCE Request B027B048 TransferBufferLength 8 Flags 3 MDL 00000000
(/srv/buildbot_cmake/full_cmake/build/lib/drivers/libusb/hub_controller.cpp:324) [USBLIB] Port 0: Status 103, Change 0
(/srv/buildbot_cmake/full_cmake/build/lib/drivers/libusb/hub_controller.cpp:324) [USBLIB] Port 1: Status 100, Change 0
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/pnpmgr/pnpmgr.c:4030) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbhub/pdo.c:541) uLan2usb convertor
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbhub/pdo.c:541) uLan2usb convertor
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/pnpmgr/pnpmgr.c:4030) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959) ZwOpenFile failed with status 0xc000003a
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/iorsrce.c:725) Failed opening given symbolic link!
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\pciide.sys at FCBF4000 with 7 pages
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\pciidex.sys at FCBEB000 with 9 pages
(/srv/buildbot_cmake/full_cmake/build/drivers/bus/pci/pdo.c:1267) Enabling command flags for PCI device 0x21 on bus 0x0: [Bus master] [I/O space enable]
(/srv/buildbot_cmake/full_cmake/build/drivers/storage/ide/pciidex/fdo.c:464) IRP_MJ_PNP / Unknown minor function 0x9
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:174) Loading: \SystemRoot\system32\drivers\ul_wdm.sys at FCBD9000 with 11 pages
Assertion 'IsListEmpty(&Irp->ThreadListEntry)' failed at /srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/irp.c line 1524
Entered debugger on embedded INT3 at 0x0008:0x80924c3a.
kdb:>
====================================================================================
Thanks for any hints in advance.
I would be happy if the problems are resolved in the future. It could be
interresting option to have livecd available with ReactOS, uLAN driver
and CHROMuLAN for us one day. We can provide even some small funding
for such achievement if it could work reliably on real hardware.
Other reason why ReactOS is interresting for us is that it has cached
some bugs in our driver (mismatch in memory pools tags which are not
reported by Windows release builds). Yet another reasons for ReactOS
is to use 64-bit ReactOS build as testbed for uLAN driver Windows 64-bit
version debugging. (64-bit Linux x86 version is fully supported now same
as MIPS, PPC and ARM). But 64-bit Windows are pain for its signing requirements
etc. And after all I do not have any (32/64-bit) Windows installed on our computers
at all so ReactOS is great target for our development even if we has to depend
on users use and demand for Windows.
As for CHROMuLAN and RectOS compatibility, chromatography system
is functional under ReactOS except for some problem in the complex
calibration files dialog which can hang the application and some
harmless exception during analysis files read.
Both seems to cause similar problems under Wine as well.
In each case, thanks for the big pile of the work invested to the
ReactOS project,
Pavel Pisa
e-mail: pisa(a)cmp.felk.cvut.cz
www: http://cmp.felk.cvut.cz/~pisa
university: http://dce.fel.cvut.cz/
company: http://www.pikron.com/
Can we rename the "Affects Version" field to "Affected Revision"? Noone
cares for 0.3.11 bugs and TRUNK ins meaningless.
Also: is it possible to automaticcally translate to the current head
revision number, when TRUNK or rather HEAD is selected? Maybe when we
have FishEye?
Regards,
Timo
Hiya
We had a little discussion tonight, regarding changes in component list.
It is obvious that current list is illogical, unplanned and requires
urgent changes, with Jira update this is the best oportunity. Initial
plan was to base upon Timo's Layout rewrite. We had just a small
trimming done - below is the result:
audio
applications
directx (or rather 3d graphics which would allow also mesa/gallium in)
host-tools
networking
ntcore
sdk
shell
usb
winedlls
win32core
+
rosdlls(
| | advapi32
| | kernel32
| | crtdll
| | lsasrv
| | msvcrt
| | msvcrt20
| | msvcrt40
| | samlib
| | samsrv
| | secur32
| | security
| | fmifs
| | vdmdbg
| | userenv
| | uext2
| | ufat
| | ufatx
| | untfs)
The problem is what to do with some ill-fitting to the current scheme,
like:
| nls
| services
| eventlog
| rpcss
| services.exe
| svchost
| umpnpmgr
| spoolsv
and more. Do you see need for more components?
--
With best regards
Caemyr
Hi,
Does anyone know how to search for issues older than 1 year or something
like that?
According to https://jira.atlassian.com/browse/JRA-1983 it should be
possible, but Icouldn't figure out how to.
Timo
Why the removal of the do/while loop?
This breaks the macro when used without braces :
+#define SepReleaseTokenLock(Token) \
+ ExReleaseResource(((PTOKEN)Token)->TokenLock); \
+ KeLeaveCriticalRegion(); \
+
<snip>
-#define SepReleaseTokenLock(Token) \
- do { \
- ExReleaseResource(((PTOKEN)Token)->TokenLock); \
- KeLeaveCriticalRegion(); \
- while(0)
<snip>
/* Release the lock if we had acquired it */
+ if (!TokenLocked) SepReleaseTokenLock(Token);
Hi,
I'd like to invite every developer to make use of the Jira planning
feature. For those, who are not yet familiar with it here's a an explantion.
In the blue Jira menu bar you'll find an item called "Agile". Click on
that to get to the planning boards.
First time users will be asked to either choose between Scrum or Kanban.
Select Scrum.
Then you will be asked to select a dashboard or create one. You can
simply choose "Scrum Board" from the dropdown list, this one should be
fine. You can later create your own board, if you like.
Now you will see 3 buttons on the right-hand side below the menu bar:
"plan", "work" and "report"
First select "plan"
On the top you can see the current "sprint", which is the next planned
period. We currently have one sprint for September. We can create
multiple sprints and periods are as we want them. I think one month is
reasonable.
Under the sprint you can see the issues that are selected for this
sprint, i.e. supposed to be tackled in that period. Currently only
project administrators can create sprints, but every developer can move
items there. To remove an item from the sprint, you need to click on it,
so it gets highlited, then open the menu with the gear wheel icon in the
issue description on the right and select "Remove from sprint".
Below you see the backlog (all open issues). Since the list is quite
huge, you can limit it to your own issues, by pressing the "Only my
issues" filter button. (Note this one works like a pushbutton, click it
once to enable, again to disable. Maybe Amine can make them look more
like that by adding a highlite color)
On the righ-hand side, you see a box that shows the currently selected
issue.
Now you can drag and drop issues from the backlog into one of the
sprints. So if you plan to work on a specific issue in September, just
drag it into sprint 1.
Now select "work"
Here you can see the so called "swim lanes". In the default Scrum Board
they are configured per Developer. So you see every developer that has
active issues in the current sprint(s). You can open and close the swim
lanes to see the issues. And you can again select "Only my issues".
The board has 3 columns: "To do", "In Progress", "Done". All issues that
you selected for the current sprint will initially be in the "To do"
column. When you work on an issue, simply drag it over to the "In
Progress" column. When you fixed it, drag it to "Done". When dragging
them the target column will be highlited in green. The "Done" column
will show you 2 fields when dragging an item there: one for resolve, one
for close. When you dragged them to close, you'll see a confirmation
dialog, where you can enter additional stuff and then confirm it.
Have fun
Timo
Hi,
I am pleased to announce the long awaited (or absolutely surprising)
release of PSEH3.
This complete from scratch rewrite takes reactos exception handling to a
new level. It comprises the following advancements:
- Use of enums instead of const variables for internal trylevel counting
and other mechanisms. enums can be declared in a nested manner as well
and only enums are treated by gcc as full compile time constants, while
const variables are treated as dynamic and are only optimized away by
the compiler later. This generally results in better optimized code.
- No more use of dynamic sized arrays. Those make the compiler emit a
slow call to _chkstk. It could have been prevented in PSEH2, if enums
had been used instead of consts. The new code uses the same registration
frame for the top level and nested levels, which also simplifies the code.
- No more use of nested function stack trampolines. These are small code
chunks that are being dynamically put on the stack, when the address of
a nested function is taken. The address of the nested function then
points to this trampoline, which sets up a pointer for nested variable
access (nested function can access variables in the parent frame). These
were parsed by PSEH2 to calculate the neccessary nested frame pointer.
PSEH3 uses a static scope table instead that contains the address of the
nested function. this is only possible by first declaring the function
and putting the implementation after the address is stored in the static
table. This is because nested functions that do not access any variables
in the parent frame do not need a stack trampoline and their addresses
are thus considered compiler constants. GCC doesn't notice that a nested
function uses variables of the parent frame, before the function is
actually implemented, so with only a prototype, it assumes a constant
address. To get the value of the parent frame pointer, PSEH2 calls the
nested function 2 times: The first time with a bogus frame pointer and a
parameter that tells the function to return the (assumed) address of the
current registration frame. Without a proper parent frame pointer the
nested function will return an offset that we can use together with the
real address of the registration frame (which we know, when calling the
filter of finally functions) to calculate the proper parent frame
pointer. The 2nd call passes a different parameter and allows the
function to do the actual work and access variables in the parent frame.
- Improved performance due to use of "asm goto". This construct allows
to get away with having labels, that are never accessed by any C code.
The compiler doesn't remove them. So we do not need the old hack, of
comparing a "volatile" 0 against 0, just to confuse GCC to not optimize
away a label. Even though there is a bug/defficiency/limitation in asm
goto, that would usually not allow the combination with static C jump
labels, we can still do that due to some tricks that force GCC to do the
right thing. More information:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51840
- Improved performance due to faster registration. The new registration
code is smaller and saves only esp and ebp. Due to some tricks in PSEH3,
GCC is forced to assume all registers are being clobbered when the
__except block is run. Filter function and __finally function don't make
use of registers from the previous code. So all neccessary register save
and restore is now fully done by GCC.
- The trick to make GCC assume all registers are clobbered at the
beginning of the __except block has one additional huge advantage. Now
all variables that are accessed by the __except block will be stored in
memory locations, so that modifications in the __try block will be
available in the __except block, something that doesn't work with PSEH2.
This does not prevent the compiler from doing constant expression
elimination! So when you try to do 2 different, constant assignments to
a variable in the __try block, expect that this will be reduced to only
the later assignment. GCC does not know, that the execution can be
interrupted in the middle of the __try block between those 2
assignments. If you need such stuff, you must use a volatile variable.
- Less stack usage. PSEH3 stores much less data on the stack. No
trampolines, only esp and ebp are saved, registration frames are smaller.
- No more need for _SEH2_YIELD(). This macro was used to make sure the
registration frames are properly unregistered, when leaving the try or
except block using goto or return. This is not neccessary anymore due to
the use of __attribute__((cleanup)). This attribute is attached to the
registration frame and causes the cleanup function to be called
automatically, whenever the variable goes out of scope. This happens
when a goto or return is used in the code.
- Human readable warnings, when special SEH instriniscs, like
_exception_info() or _abnormal_termination() are used outside of their
valid context.
- Cleaner and better readable code, so you won't get braindead, when
trying to figure out what's going on. Header: < 300 lines commented
code, instead of 370 lines uncommented code, lib: < 250 lines of
commented C code + < 70 lines commented asm code, instead of 290 lines
of uncommented C code + 120 lines uncommented asm code)
I also promised Amine to take a look into implementing a version that is
compatible with clang. Initially I planned to include this into this
release, but it turns out that clang massivley lacks features to do so
and a completely different approach will probably be used for that.
The new code is only compatible with GCC 4.7 and later, and it's also
currently disabled (cmake option USE_PSEH3).
Tesbot showed no noticable regressions.
Have fun.
Timo
Hello,
I turned off Bugzilla now in favor of finishing the switch to JIRA.
Once the work is done, I will announce either return to Bugzilla or
introduce JIRA.
Hopefully, it'll be the latter option.
Best regards,
Aleksey.
This commit breaks msvc compilation.
Best regards
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Subject: buildbot failure in ReactOS on CMake_x86_MSVCWin Debug
Date: Tue, 04 Sep 2012 03:10:09 +0000
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/1908
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_1
Build Reason: scheduler
Build Source Stamp: 57233
Blamelist: cgutman
BUILD FAILED: failed building bootcd
sincerely,
-The Buildbot
--
With best regards
Caemyr
Currently, we experience random crashes in 2nd stage. I was unable to
catch any first exception bar the one with vmware detection code (which
is outdated and should be removed).
After forcing build again, test run failed at Cleanup, due to
previously unresolved issue of repeating whole testrun when crash
occurs in APItests.
On Mon, Sep 3, 2012, at 10:21 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/6496
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: The web-page 'force build' button was pressed by 'osiejka':
>
> Build Source Stamp: 57227
> Blamelist:
>
> BUILD FAILED: failed Cleanup
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr
This one is caused by rev 57225:
Backtrace:
http://www.reactos.org/paste/index.php/10472/
Please fix
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
Date: Sun, 02 Sep 2012 22:50:06 +0000
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/6492
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: 57225
Blamelist: ion
BUILD FAILED: failed test
sincerely,
-The Buildbot
--
With best regards
Caemyr
Hiya
R3ddr4g0n reported to me that all recent revisions uploaded to
iso.reactos.org are not correct. Instead of given revision, all the
builds are reporting to be rev 57150. After a quick check, i downloaded
bootcd-57221-dbgwin.iso and checked its SHA1: should be
56d2190610e8a1f650faa3c6a6a8348f89d1fa1b but happened to be:
f97ac4aba0e5ceed3b5beae3d7ab2bc2c7600fab - which is indeed the same
checksum as for x86_CMake-57150
The possible clue from the upload script:
bash: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at
/home/lapo/package/rsync-3.0.8-1/src/rsync-3.0.8/io.c(601)
[sender=3.0.8]
* Done.
* Remotely compressing bootcd-57219-dbgwin...
Now, Colin may recall that i was strongly against using fancy tricks for
sending the revs instead of simply archiving them locally and uploading
afterwards. This way with rsync was supposed to be saving bit of
bandwidth.
Now we have to reupload at least all since 57150, unless you can use the
fancy tricks to spot the same iso files. Great thing we can save a
little bit of bandwidth but waste time to fix it afterwards.
Accoring to the reporter:
[21:45:37] <r3ddr4g0n> for sure from 57115 to 57221
If you still think this methode is saving us anything, please reckon
that a single view of testbot log means downloading a few megabytes of
text at least.
I`m stopping the uploads until the problem is resolved in a way to
prevent it from happening again.
--
With best regards
Caemyr
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 30th of August, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting, if the server works. If not, then an alternative
place will be announced here. Note that the IRC service will only be
started shortly before the meeting. Your participation passwords will be
emailed to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. As usual, Z98 is welcome to volunteer.
The agenda will be posted shortly before the meeting, suggestions are
welcome (send them to my email as usual).
With the best regards,
Aleksey Bragin.
Hi,
I don't agree with these changes.
If we need a DllEntry in the lib, then we should use the one that is
provided by mingw-w64 (all this code is 100% mingw-w64). It simply
returns true (thats exactly what the one in MS CRT does) and works for
gcc and MSVC.
Also what's the point of DisableThreadLibraryCalls() here? As you wrote
yourself, no DllMain only means "I have nothing more to initialize than
the CRT". But this disables the CRT thread initializion, too.
There is also no need for weak symbols, we can simply call the stub
DllMain, since it doesn't (shouldn't) do anything.
Regards,
Timo
Am 27.08.2012 01:31, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Sun Aug 26 23:31:49 2012
> New Revision: 57171
>
> URL: http://svn.reactos.org/svn/reactos?rev=57171&view=rev
> Log:
> [MINGWEX]
> - mark DllMain as a weak symbol for GCC.
> - supply a stubbed DllMain for MSVC.
> - DllMain is optional, and some DLLs don't implement it. That doesn't mean that they have no entry point, it means "I have nothing more to initialize than the CRT".
>
> Added:
> trunk/reactos/lib/sdk/crt/startup/mscdllmain.c (with props)
> Modified:
> trunk/reactos/lib/sdk/crt/msvcrtex.cmake
> trunk/reactos/lib/sdk/crt/startup/crtdll.c
>
> Modified: trunk/reactos/lib/sdk/crt/msvcrtex.cmake
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/crt/msvcrtex.cmake…
> ==============================================================================
> --- trunk/reactos/lib/sdk/crt/msvcrtex.cmake [iso-8859-1] (original)
> +++ trunk/reactos/lib/sdk/crt/msvcrtex.cmake [iso-8859-1] Sun Aug 26 23:31:49 2012
> @@ -66,7 +66,9 @@
> endif()
>
> if(MSVC)
> - list(APPEND MSVCRTEX_SOURCE startup/mscmain.c)
> + list(APPEND MSVCRTEX_SOURCE
> + startup/mscmain.c
> + startup/mscdllmain.c)
> else()
> list(APPEND MSVCRTEX_SOURCE startup/gccmain.c)
> endif()
>
> Modified: trunk/reactos/lib/sdk/crt/startup/crtdll.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/crt/startup/crtdll…
> ==============================================================================
> --- trunk/reactos/lib/sdk/crt/startup/crtdll.c [iso-8859-1] (original)
> +++ trunk/reactos/lib/sdk/crt/startup/crtdll.c [iso-8859-1] Sun Aug 26 23:31:49 2012
> @@ -50,7 +50,19 @@
>
> extern int mingw_app_type;
>
> +/*
> + * It is possible that a DLL provides no DllMain entry point.
> + * Mark it as a weak symbol for GCC.
> + * Tests show that at link time, MSVC looks for a function first in the object files provided, and then
> + * in the libraries. This means that we must provide a basic implementation in msvcrtex, which will be used
> + * if none is found in the object files provided to link.exe.
> + * This also means that we can't rely on a DllMain function implemented in a static library when linking a DLL.
> + */
> +#ifdef __GNUC__
> +extern WINBOOL WINAPI DllMain (HANDLE hDllHandle, DWORD dwReason, LPVOID lpreserved) __attribute__((weak));
> +#else
> extern WINBOOL WINAPI DllMain (HANDLE hDllHandle, DWORD dwReason, LPVOID lpreserved);
> +#endif
>
> extern WINBOOL WINAPI DllEntryPoint (HANDLE, DWORD, LPVOID);
>
> @@ -198,10 +210,12 @@
> }
> if (dwReason == DLL_PROCESS_ATTACH)
> __main ();
> - retcode = DllMain(hDllHandle,dwReason,lpreserved);
> + if(DllMain)
> + retcode = DllMain(hDllHandle,dwReason,lpreserved);
> if (dwReason == DLL_PROCESS_ATTACH && ! retcode)
> {
> - DllMain (hDllHandle, DLL_PROCESS_DETACH, lpreserved);
> + if(DllMain)
> + DllMain (hDllHandle, DLL_PROCESS_DETACH, lpreserved);
> DllEntryPoint (hDllHandle, DLL_PROCESS_DETACH, lpreserved);
> _CRT_INIT (hDllHandle, DLL_PROCESS_DETACH, lpreserved);
> }
>
> Added: trunk/reactos/lib/sdk/crt/startup/mscdllmain.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/crt/startup/mscdll…
> ==============================================================================
> --- trunk/reactos/lib/sdk/crt/startup/mscdllmain.c (added)
> +++ trunk/reactos/lib/sdk/crt/startup/mscdllmain.c [iso-8859-1] Sun Aug 26 23:31:49 2012
> @@ -1,0 +1,11 @@
> +#include <oscalls.h>
> +#define _DECL_DLLMAIN
> +#include <process.h>
> +
> +WINBOOL WINAPI DllMain (HANDLE hDllHandle, DWORD dwReason, LPVOID lpreserved)
> +{
> + /* If the DLL provides no DllMain, then chances are that it doesn't bother with thread initialization */
> + if(dwReason == DLL_PROCESS_ATTACH)
> + DisableThreadLibraryCalls(hDllHandle);
> + return TRUE;
> +}
>
> Propchange: trunk/reactos/lib/sdk/crt/startup/mscdllmain.c
> ------------------------------------------------------------------------------
> svn:eol-style = native
>
>
>
Btw, we are using a lot of hardcoded 512 values here for sector size
even though there is a field in fthe Volume structure for that.
Is that correct?
Am 23.08.2012 14:02, schrieb tkreuzer(a)svn.reactos.org:
> Author: tkreuzer
> Date: Thu Aug 23 12:02:30 2012
> New Revision: 57141
>
> URL: http://svn.reactos.org/svn/reactos?rev=57141&view=rev
> Log:
> [FREELDR]
> Improve readability of sector calculation
>
> Modified:
> trunk/reactos/boot/freeldr/freeldr/fs/fat.c
>
> Modified: trunk/reactos/boot/freeldr/freeldr/fs/fat.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/freeldr/fs/fa…
> ==============================================================================
> --- trunk/reactos/boot/freeldr/freeldr/fs/fat.c [iso-8859-1] (original)
> +++ trunk/reactos/boot/freeldr/freeldr/fs/fat.c [iso-8859-1] Thu Aug 23 12:02:30 2012
> @@ -1338,8 +1338,7 @@
> //
> // Seek to right position
> //
> - Position.HighPart = SectorNumber >> 23;
> - Position.LowPart = SectorNumber << 9;
> + Position.QuadPart = (ULONGLONG)SectorNumber * 512;
> ret = ArcSeek(Volume->DeviceId, &Position, SeekAbsolute);
> if (ret != ESUCCESS)
> {
>
>
>
Hi,
On 2012-08-26 11:17, jgardou(a)svn.reactos.org wrote:
> Log:
> [OPENGL32_WINETEST]
> - Sync with wine
speaking from previous experience, it'd be very nice if the commit
message would allow finding the correctly matched Wine version for this
easily (i.e. without tedious look-up of what was HEAD on whatever date
the commit was).
Thanks!
Best regards,
Thomas
Hi,
after having finished its 11405th build, the last official RBuild
builder has gone offline, forever.
The Linux CMake builder has now turned as being the official builder.
Thanks RBuild, you served us well :-).
Also, the other RBuild builder, the release builder has also gone
offline forever. Its hardware was not able to properly handle a ReactOS
build, and was hardly upgradable.
Daily release builds should replace it any time soon.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Hi,
On 2012-08-21 15:38, jgardou(a)svn.reactos.org wrote:
> URL:http://svn.reactos.org/svn/reactos?rev=57124&view=rev
> Log:
> [WINED3D]
> - MSVC needs INFINITY and NAN from wine/port.h.
> It can't be included from a header
> Will be sent upstream
can you explain what's wrong with including it from a header?
I was under the impression we had fixed the infinity/nan stuff properly
on Wine's side by adding it all to port.h.
Thanks!
-Thomas
Hmmmmmmm....
I don't think that this is a good idea. We must call DC_vPrepareForBlit
to lock the surfaces, otherwise we run into race conditions.
And we should really also care for the mouse cursor, otherwise we might
make it unhappy.
Anyway, I don't care about this code, since I already rewrote it :D
Anyway, I think it's time to ASSERT device locks.
Am 22.08.2012 18:45, schrieb jgardou(a)svn.reactos.org:
> Author: jgardou
> Date: Wed Aug 22 16:45:49 2012
> New Revision: 57129
>
> URL: http://svn.reactos.org/svn/reactos?rev=57129&view=rev
> Log:
> [WIN32K]
> - Use the right surface for direct DCs in DIB transfer functions
> It could have changed with a display settings change
>
> Modified:
> trunk/reactos/win32ss/gdi/ntgdi/dibobj.c
>
> Modified: trunk/reactos/win32ss/gdi/ntgdi/dibobj.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/win32ss/gdi/ntgdi/dibobj.c…
> ==============================================================================
> --- trunk/reactos/win32ss/gdi/ntgdi/dibobj.c [iso-8859-1] (original)
> +++ trunk/reactos/win32ss/gdi/ntgdi/dibobj.c [iso-8859-1] Wed Aug 22 16:45:49 2012
> @@ -447,8 +447,16 @@
> DC_UnlockDc(pDC);
> goto Exit2;
> }
> -
> - pSurf = pDC->dclevel.pSurface;
> +
> + /*
> + * Select the right surface.
> + * NOTE: we don't call DC_vPrepareDCsForBlit, because we don't
> + * care about mouse, visible region or brushes in this API.
> + */
> + if(pDC->dctype == DCTYPE_DIRECT)
> + pSurf = pDC->ppdev->pSurface;
> + else
> + pSurf = pDC->dclevel.pSurface;
> if (!pSurf)
> {
> DC_UnlockDc(pDC);
> @@ -1113,7 +1121,15 @@
> goto cleanup;
> }
>
> - psurfDst = pdc->dclevel.pSurface;
> + /*
> + * Select the right surface.
> + * NOTE: we don't call DC_vPrepareDCsForBlit, because we don't
> + * care about mouse, visible region or brushes in this API.
> + */
> + if(pdc->dctype == DCTYPE_DIRECT)
> + psurfDst = pdc->ppdev->pSurface;
> + else
> + psurfDst = pdc->dclevel.pSurface;
> if (!psurfDst)
> {
> // CHECKME
>
>
>
For me it looks like _pwctype, __p__pwctype and __pwctype_func also
need to be fixed.
Am 20.08.2012 19:20, schrieb fireball(a)svn.reactos.org:
> Author: fireball
> Date: Mon Aug 20 17:20:48 2012
> New Revision: 57119
>
> URL: http://svn.reactos.org/svn/reactos?rev=57119&view=rev
> Log:
> [CRT]
> - Use wine's wctype table in CRT for iswctype() function. Previous implementation was returning incorrect information for non-Latin characters. Problem found and fixed by Sergey Shamanaev (seven_ro).
> - Move wctype.c from libwine to lib/sdk/crt instead of making yet another copy of it (currently there is one more in tools/unicode). Suggested by Amine Khaldi.
> See issue #5090 for more details.
>
> Added:
> trunk/reactos/lib/sdk/crt/string/wctype.c
> - copied unchanged from r57101, trunk/reactos/lib/3rdparty/libwine/wctype.c
> Removed:
> trunk/reactos/lib/3rdparty/libwine/wctype.c
> Modified:
> trunk/reactos/lib/3rdparty/libwine/CMakeLists.txt
> trunk/reactos/lib/sdk/crt/crt.cmake
> trunk/reactos/lib/sdk/crt/string/ctype.c
>
> [This mail would be too long, it was shortened to contain the URLs only.]
>
> Modified: trunk/reactos/lib/3rdparty/libwine/CMakeLists.txt
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/3rdparty/libwine/CMake…
>
> Removed: trunk/reactos/lib/3rdparty/libwine/wctype.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/3rdparty/libwine/wctyp…
>
> Modified: trunk/reactos/lib/sdk/crt/crt.cmake
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/crt/crt.cmake?rev=…
>
> Modified: trunk/reactos/lib/sdk/crt/string/ctype.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/lib/sdk/crt/string/ctype.c…
>
>
>
Hi,
today, many of our services encountered a long downtime due to an air
conditioning issue in the datacenter their running hypervisor is located
(you can find more info there: http://hetzner-status.de/ - german).
A safety shutdown has been done to preserve our server hardware
integrity.
The other hypervisor and the other services being in other datacenters,
they were not concerned by the issue.
Services being concerned:
- Mail
- SVN
- git
- web
- build master
They are now fully back online and operational.
Sorry for the inconvenience.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Dear All
Some time ago, due to lack of space on ROS servers, a large number of
old ISO files for prebuilt revisions had to be deleted. I was only able
to pull a limited number of them. Right now, while hunting a regression
in late rev 3xxxx, i`m heavily limited due to lack of ISOs. For a
long-term plan, i intend to add a legacy builder, containing all the
previous, rbuild-based Build environments, allowing me to build some
really old revs. Right now i need to ask for your assistance.
If you have any older, OFFICIAL Bootcd ISO files, of revision earlier
than 44000, please let me know, be it on irc or by forum PM. We need to
compare the revisions first, to avoid duplicates, then i`ll pull them
from you onto my server, which will effectively allow our Team to use
them if needed.
Thanks in advance.
--
With best regards
Caemyr
It seems that any crash in APITESTS on vbox testbot is causing
rosautotest to redo from start. We can see this in stdio log:
http://build.reactos.org/builders/Windows_AMD64_1%20VBox-Test/builds/6323/s…
(just search for "restarting" word). APITESTS are repated and such log
as a whole is messing up testman, which is treating it like two
submissions for the same revision. It accepts the first one (incomplete
due to crash) and rejects the second one, reporting a duplicate: "ERROR!
submit(13111, 518, ...) - We already have a result for this test suite
in this test run! "Windows_AMD64_1 VBox-Test""
As we all know, we should expect tests to fail and even crash (this is
what they are designed for), hence the error is in rosautotest and
testman.
Rosautotest, strangely, is affected only on vbox, on kvm the apitest
crash is not causing a restart of test run. Winetests, if i recall
correctly, were never affected in such way.
Testman should not reject a submission after its saved up and revision -
blocked.
I am aware that some will be tempted to comment out the test in
question, but this is not a proper solution to this situation. Other
apitest will crash in the future, bringing the whole thing back. Same as
with regressions, lack of tests due to such issue, will bite us back in
the future, when least expected and most needed. This is why I humbly
request this issue to be solved properly, once and for all.
With best regards
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
Date: Tue, 14 Aug 2012 00:23:24 +0000
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/6324
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: 57075
Blamelist: akhaldi
BUILD FAILED: failed Cleanup
sincerely,
-The Buildbot
--
With best regards
Caemyr
http://www.reactos.org/bugzilla/show_bug.cgi?id=6035
--- Comment #7 from hbelusca <hermes.belusca(a)sfr.fr> 2012-08-09 14:02:29 CET ---
According to Edijs, the confirmation message box isn't in top-most position
with respect to the Abiword's window :
[15:57:09] <Edijus> hbelusca: When save changes dialog appears, change focus to
explorer or some other window.
http://www.reactos.org/bugzilla/show_bug.cgi?id=6035
[15:57:26] <Edijus> hbelusca: Save changes dialog is not top most. Report it,
please. :)
[15:59:47] <hbelusca> Edijus: you mean that the confirmation message box of
Abiword can "disappear" (ie. go behind another window) ?!
[16:00:25] <Edijus> hbelusca: Yeah. Check if it reported or not, before
reporting.
[16:00:32] <Edijus> Thanks.
--
Configure bugmail: http://www.reactos.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
_______________________________________________
Ros-bugs mailing list
Ros-bugs(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-bugs
The ReactOS Project is proud to announce the first of the development
contracts that will be funded by the recent donation campaign. Edijs
Kolesnikovics joined the ReactOS development team very recently and
has been working extensively with Amine Khaldi and Olaf Siejka to
create an application test suite based around the AutoHotkey (AHK)
automation system. AutoHotkey is a tool for scripting keyboard and
mouse actions in order to automate running of programs on Windows.
While the current test suites exercise a considerable amount of
functionality, the true test for ReactOS remains when it is used to
run applications. As such, Edijs has been working to create tests
using AHK to run a variety of applications, starting with those on the
Golden Apps list. The basic framework is already in place along with a
few tests, but much more can be done to expand the selection of
applications tested. As such, the Foundation has elected to grant
Edijs a development contract to develop additional tests. The project
congratulates Edijs on a job well done so far, and would also like to
thank Amine, Olaf, and the AHK developers for their help mentoring and
advising Edijs.
Contract Details
Time: 84 hours minimum
Wage: €168
Expected Duration: 1 month
Objective: Within the designated time period, develop as many AHK test
scripts for applications to be used with the automated regression
testing as possible. The intended goal is to have at least all
remaining Golden Apps testable. This project seeks to help developers
catch regressions more quickly so that stabilizing ReactOS for
releases becomes less time consuming. This task will be monitored by
Amine Khaldi.
Sidenote: Due to a variety of circumstances unrelated to the donation
campaign, Edijs' contract wage is significantly lower than what would
be the standard contract wage for the project.
While this works for us, we should consider trying to get this feature
back. When it's considered for removal, then they obviously "fixed"
something now that noone needs (and that makes absolutely no sense at
all), while the feature as it was before is very useful to compile 3rd
party code for Windows.
One possibility (since we compile gcc ourselves anyway), is finding out
where they "fixed" it and revert that revision for our builds. If they
completely remove it, we rename the option and send the old code in as a
new feature for MSVC compatibility ;-)
Am 29.07.2012 03:49, schrieb akhaldi(a)svn.reactos.org:
> Author: akhaldi
> Date: Sun Jul 29 01:49:24 2012
> New Revision: 56973
>
> URL: http://svn.reactos.org/svn/reactos?rev=56973&view=rev
> Log:
> [CLASSPNP]
> * Explicitly mark the functions as stdcall (NTAPI).. -mrtd changes the default calling convention, but name-decoration isn't affected by this. The -mrtd feature has its origin in some older linux-code-mode, and it's considered for removal in GCC 4.8.
> * Fix some warnings.
>
> Modified:
> trunk/reactos/drivers/storage/classpnp/CMakeLists.txt
> trunk/reactos/drivers/storage/classpnp/autorun.c
> trunk/reactos/drivers/storage/classpnp/class.c
> trunk/reactos/drivers/storage/classpnp/classp.h
> trunk/reactos/drivers/storage/classpnp/classwmi.c
> trunk/reactos/drivers/storage/classpnp/clntirp.c
> trunk/reactos/drivers/storage/classpnp/create.c
> trunk/reactos/drivers/storage/classpnp/dictlib.c
> trunk/reactos/drivers/storage/classpnp/lock.c
> trunk/reactos/drivers/storage/classpnp/obsolete.c
> trunk/reactos/drivers/storage/classpnp/power.c
> trunk/reactos/drivers/storage/classpnp/retry.c
> trunk/reactos/drivers/storage/classpnp/utils.c
> trunk/reactos/drivers/storage/classpnp/xferpkt.c
>
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 26th of July, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. As usual, volunteers are welcome.
he agenda will be posted shortly before the meeting, suggestions are
welcome (send them to my email as usual).
With the best regards,
Aleksey Bragin.
May I attend? I am not a developer, nor do I know the way these types of
meetings take place.
I would like to observe and possibly take notes for PR releases.
I apologize for my late request; I just signed up for this 'dev list'.
If nothing else, could someone send me the log from the meeting? Thank you
in advance. :)
Ben Rossington
On Wed, Jul 25, 2012 at 8:00 AM, <ros-dev-request(a)reactos.org> wrote:
> Send Ros-dev mailing list submissions to
> ros-dev(a)reactos.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://www.reactos.org/mailman/listinfo/ros-dev
> or, via email, send a message with subject or body 'help' to
> ros-dev-request(a)reactos.org
>
> You can reach the person managing the list at
> ros-dev-owner(a)reactos.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Ros-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Monthly meeting - July 2012 (Javier Agust?n Fern?ndez Arroyo)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 24 Jul 2012 20:48:25 +0200
> From: Javier Agust?n Fern?ndez Arroyo <elhoir(a)gmail.com>
> To: ReactOS Development List <ros-dev(a)reactos.org>
> Subject: Re: [ros-dev] Monthly meeting - July 2012
> Message-ID:
> <
> CAAHf8rfhEmOvydFSfJPrY1Y3ArPZU8oeAr4as0tQ_Fn1pKwenA(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> hi there
> im on holydays, so i wont be at the meeting
>
> Sorry,
>
> On Tue, Jul 24, 2012 at 11:52 AM, Sylvain Petreolle <spetreolle(a)yahoo.fr
> >wrote:
>
> > I may be unable to attend this meeting.
> > I don't know if www/IRC will be available at my holidays place.
> >
> > Kind regards,
> > Sylvain Petreolle
> >
> > ------------------------------
> > *De :* Aleksey Bragin <aleksey(a)reactos.org>
> > *? :* ReactOS Development List <ros-dev(a)reactos.org>
> > *Envoy? le :* Mardi 24 juillet 2012 11h10
> > *Objet :* [ros-dev] Monthly meeting - July 2012
> >
> > Hello,
> > Let me invite you to the monthly status meeting taking place last
> Thursday
> > of this month, 26th of July, 19:00 UTC.
> >
> > The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
> > the channel #meeting. Note that the IRC service will only be started
> > shortly before the meeting. Your participation passwords will be emailed
> to
> > you shortly before the meeting starts.
> > If someone still is not getting passwords sent before a meeting - please
> > email Colin or Pierre before the meeting started to get one.
> >
> > In order to save time, let's choose who is going to be the minute taker
> on
> > the upcoming meeting. As usual, volunteers are welcome.
> >
> > he agenda will be posted shortly before the meeting, suggestions are
> > welcome (send them to my email as usual).
> >
> > With the best regards,
> > Aleksey Bragin.
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
Hi,
FireFox 3.0.19 can be found here:
ftp://archive.mozilla.org/pub/firefox/releases/3.0.19-real-real/win32/en-US…
I definitely don't see why we should host it. This link won't change
(since it's Mozilla archive).
Why uploading Click-N-Type on our server while they provide a link that
won't change with version upgrade: http://cnt.lakefolks.com/CNTzip.exe
Once again, I definitely don't see why we should host it.
Same with FireFox 3.6.28:
ftp://archive.mozilla.org/pub/firefox/releases/3.6.28/win32/en-US/Firefox%2…
So, there's no reason why we should host it.
TotalCommander can be found on an official mirror site here:
http://www.slo.ru/download/total_commander/tcm80x32.exe
Since it's a shareware software, I see no reason why we should host it.
Furthermore, it might cause issues with license.
Finally, as for the rest, Thunderbird 3.1.20 can be found here:
ftp://archive.mozilla.org/pub/thunderbird/releases/3.1.20/win32/en-US/Thund…
So, I definitely don't see why we should host it.
Please delete all the the files above from our server, and use the links
I provided.
Only host applications that we cannot find in a TRUSTED place, or
applications that we ship with our own modifications.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Hi,
Around 56843 to 56917 I've been forced to do a mass clean to build the
bootcd!!!! This has put a halt for me to work on ReactOS while it
takes 33+ minutes to build. Example, makex XXXXX_clean does not work
at all even when removing bootcd.iso! Forcing to clean in the main
checkout directory! Posted this twice on IRC!
Hello,
I want to share that I just had a pleasure to meet Jan "JaixBly" two
days ago in Sweden once again. We discussed many ReactOS-related topics,
and had fun with a newly delivered Raspberry Pi.
We've covered future plans for ReactOS development, testing
infrastructure, Samba integration, ARM processors support and many other
things.
A photo when we took a break from trying to get WiFi working in
Raspberry Pi and went outside: http://savepic.org/2407687.jpg
Best regards,
Aleksey Bragin.
Hi all,
My name is Simon and I am blind.
I saw in the archives that there was a short subject about
accessibility in ReactOS in 2010.
The NVDA screenreader was tested there and wasn't working.
Can someone tell me the current status of this?
Maybe there could be a collaboration between ReactOS devs and NVDA
devs to get accessibility in ReactOS?
NVDA can be found on www.nvda-project.org.
Daily snapshots can be found on
http://nvda.sf.net/snapshots/.index.html
Just some thoughts.
Greetings from Austria,
Simon
Fantastic!
Smss2 will be happy :)
-----Original Message-----
From: ros-diffs-bounces(a)reactos.org [mailto:ros-diffs-bounces@reactos.org] On Behalf Of ion(a)svn.reactos.org
Sent: 16 July 2012 00:42
To: ros-diffs(a)reactos.org
Subject: [ros-diffs] [ion] 56906: [NTOSKRNL]: Implement support for session pool (not yet enabled) and session space (implemented and enabled, but nobody is calling the APIs yet). [NTOSKRNL]: Implement MmMapViewOInSess...
Author: ion
Date: Sun Jul 15 23:42:27 2012
New Revision: 56906
URL: http://svn.reactos.org/svn/reactos?rev=56906&view=rev
Log:
[NTOSKRNL]: Implement support for session pool (not yet enabled) and session space (implemented and enabled, but nobody is calling the APIs yet).
[NTOSKRNL]: Implement MmMapViewOInSessionSpace, MmUnmapViewInSessionSpace. Win32k needs to use these to we can test them.
Modified:
trunk/reactos/ntoskrnl/mm/ARM3/i386/init.c
trunk/reactos/ntoskrnl/mm/ARM3/miarm.h
trunk/reactos/ntoskrnl/mm/ARM3/pfnlist.c
trunk/reactos/ntoskrnl/mm/ARM3/pool.c
trunk/reactos/ntoskrnl/mm/ARM3/procsup.c
trunk/reactos/ntoskrnl/mm/ARM3/section.c
Hi,
I've noticed that the ROS-Diffs list (or rather the hook sending to it)
consistently fails on revisions that have special chars in their commit
message.
E.g. there is no message for r56846, r56844, r56763, r56754 etc.
(sorry Hermès :p)
This goes back as far as r23711 (August 2006), for which the archive
shows no message [1].
It apparently did work at some point because r20354 (December 2005) and
earlier seem to have ROS-Diffs messages [2] (although possibly because
special chars didn't make it into the mails' subjects).
Is there a chance this could be fixed?
And in the meantime, could I ask the devs to refrain from using special
chars? (don't know about you, but the missing messages are quite an
annoyance to me, as this is the most convenient platform for code
review)
Thanks!
-Thomas
[1] http://www.reactos.org/pipermail/ros-diffs/2006-August/thread.html
[2] http://www.reactos.org/pipermail/ros-diffs/2005-December/010731.html
July 2012 Meeting A Minutes
2012-07-05
19:00 UTC
dev.reactos.org, #meeting
Proceedings
===========
* Meeting started at 19:16 UTC by Aleksey Bragin.
* Point 0: CD/Product Store
* Point 1: Update/Team Plan
* Point 2: Website Update
* Point 3: Internet Declaration
Due to scheduling constraints by some participants, the question of a
team store and sale of ReactOS CDs was moved to be the first topic.
* Point 0
Ziliang Guo presented the question of CD sales and merchendise sales
in general. Amine Khaldi updated the team on the work he and others
have done to get storefronts up and going. The primary concern was a
lack of decent designs for the stores. Ziliang was tasked with
contacting graphic artists he knows in the community to see if this
can be remedied. The decision of what to do with the promo CDs was
left to Ziliang as well.
* Point 1
Aleksey Bragin stated that he intended to help with Jira integration
with the new site, which is necessary as a replacement for bugzilla.
He also hopes to help with making the build environment more user
friendly.
Olaf Siejka reported on a variety of regressions in freeldr and the
win32 subsystem that he wants fixed as they are blocking further
development and testing. Other developers asked for specific reports
to be assigned to them and reviewed whether they thought they knew the
cause of regressions.
Collaboration with the UniATA developer was also discussed, with
reports that upstream patches have been accepted and suggestions on
further work that can be done.
* Point 2
Danny Gotte was not present so this point was skipped.
* Point 3
Pierre Schweitzer presented the Internet Declaration
(http://www.internetdeclaration.org/freedom), a statement of beliefs
drafted by various groups that wish the internet to remain free of
censorship and ensure user privacy. Many other organizations have
signed onto it and Pierre asked whether the ReactOS Foundation should
also do so. This was put to a vote and passed with overwhelming
support.
* Other Decisions
Ziliang requested that all developers be added onto the public
relations mailing list. This was approved.
Meeting was closed at 20:38 by Aleksey Bragin
Minutes were prepared by Ziliang Guo
Hello!
I was away this week, so the meeting at the usual time got canceled.
I propose to conduct meeting next thursday, 5th of July. If someone
would not be able to make it - please email me.
Regards,
Aleksey Bragin.
Hello everyone!
I just got freeldr working properly (sort of) on the iPhone 4!
Currently, I use Apple's iBSS
(first stage DFU bootloader), with the go command patched to always branch to
0x41000000. 0x41000000 contains the actual LLB, which is relocated to
0x42000000.
The LLB will initialize the ReactOS loader console and ARM loader
block, which is sent
to FreeLoader, just like on Omap3/Zoom2MDK and Versatile/PB.
Time to get ramdisks working. :)
http://goput.it/uc5.jpg <- There's your picture.
-- winocm
Barring any last minute hiccups, we expect to have a meeting this
Thursday. I am sending out this email because we have a PR topic we need
to discuss and I would like as many devs present as possible, and
considering Aleksey is likely asleep by now, I felt we needed this out
before "tomorrow" to give people enough heads up. Aleksey can make a more
formal announcement with other agenda points if he has them.
Z
Hi,
we are currently working on the failed server to fix it definitely (we
hope). I have set up a temporary solution to ensure ISOs are well
stored.
They cannot be downloaded though.
Sorry about all that troubles.
With my best regards,
P. Schweitzer
On Tue, 2012-06-26 at 08:43 +0000, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/998
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 56807
> Blamelist: tfaber
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Hi,
this is unfortunately due to our entry server to network storage that
has crashed once again tonight. All attempts to remotely reboot it
failed. A human intervention will be required. It will not happen before
several hours. The responsible person for the server has been informed.
In case it was not possible to restore the server in a correct time, a
workaround solution will be deployed once again.
We are sorry for the caused inconvenience.
With my best regards,
P. Schweitzer
Le dimanche 24 juin 2012 à 21:10 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/989
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 56800
> Blamelist: ekohl
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Greetings All,
I am new to ReactOS but have much experience with with Windows, Linux,
etc... as well as programming mainly in C/C++.
Recently, I have decided to looking into ReactOS from a learning
perspective after which, once the learning curve has been completed, I may
try to get involved with some of the development efforts as well as work on
some additional projects.
>From what I have seen, ReactOS has come a very long ways in its development
and is really turning into a special OS to be recognized.
I would like to review some of the documentation on the Wiki but had a
question regarding an experiment that I wanted to investigate with ReactOS.
The question that I wanted to answer is this.
What is the absolute minimum size, as relates to booting and OS files that
are needed by ReactOS to run, for example, the notepad.exe program?
To caveat this, it would include leaving out all of the OS tools, Explorer,
Desktop, and absolutely everything that is not clearly needed to run the
notepad.exe application.
Basically, I would like ReactOS to boot and go directly into the notepad
application. The real point here is to investigate what "absolute" minimum
files are needed to run a simple application.
Sounds a bit crazy, but that is the question that I would like to answer.
Any ideas or information related to this would be greatly appreciated.
Thanks and have a great day,
Lonnie
Greetings All,
I have been reviewing ReactOS on the website and wiki to get a better feel
for the project, which I must say is very impressive.
>From what I have read, it seems that ReactOS is initially shooting for a
drop-in replacement for WindowsXP and beyond which raised a question for
me. The site also seems to suggest, for the most part and with the
exception of a few core ReactOS files (ie. kernel plus a couple of others),
that ReactOS should be 100% compatible with WindowsXP.
With this in mind, I wondered this. If I had an old licensed Windows XP
disk, which I do, then shouldn't it be possible to use the base core
ReactOS files (ie. the minimalist ReactOS configuration like in my previous
inquiry to the mailing list) and then use the WindowsXP subsystem core
files?
I guess what I was wondering, not to detract from the true developments of
ReactOS which I like a lot, is would the WindowsXP system files function
the same with the ReactOS kernel, and minimal files that were listed by
Alex in a previous email.
reeldr (ntldr)
ntoskrnl
hal
bootvid
kdcom
fastfat
ramdisk
kbdclass
i8042prt
ntdll
smss
What I am getting at, is a development that is still forming, but the idea
is to utilize ReactOS to allow for the development of a Super Sandbox
system that is run in a specialize VM, and which would allow for each
application to be run in their own ReactOS VM. Although I am still playing
with the idea a lot, it is forming in such a way that would totally isolate
each application in a separate VM that is composed of super minimal ReactOS
kernel running.
Just playing with ideas that I have had for a while, but at the moment, I
am still learning about ReactOS so that I will be able to contribute to it
soon.
Thanks and have a great day,
Lonnie
Hello,
it's time for my periodical rant about debug log mess again. The example
below is made using latest VirtualBox 3.
Suggestions and questions:
1. usbohci - it's left on intentionally to better aid debugging?
Allright, however I think these lines
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbohci/hardware.cpp:1199)
Waiting 0 milliseconds for port power up
(/srv/buildbot_cmake/full_cmake/build/drivers/usb/usbohci/hardware.cpp:1145)
Enabling status change
repeated 8 times is a little bit too much.
Same about libusb listing statuses of all ports. Which goes on yet
another time with EHCI controller.
2. What are these lines? Repeated 14 times
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:2959)
ZwOpenFile failed with status 0xc000003a
3. What happened to the floppy driver?
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:1579)
'\Driver\FLOPPY' initialization failed, status (0xc000000e)
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:61)
Deleting driver object '\Driver\FLOPPY'
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:87)
HACK: Not unloading the driver image due to critical bugs!
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/io/iomgr/driver.c:1961)
IopInitializeDriver() failed (Status c000000e)
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/sysldr.c:935)
Leaking driver: floppy.sys
Fix it? Don't enable it in trunk builds if it's buggy and not fixed?
4. These lines repeated 20 times.
(/srv/buildbot_cmake/full_cmake/build/dll/ntdll/ldr/ldrapi.c:811)
NtCreateSection() failed (Status 0xc0000022).
Why creating section in LdrpVerifyImageMatchesChecksum() failes now?
5. Win32 stage.
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/winsta.c:208)
err: Invalid window station handle
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/ntuser.c:161)
err: Enter NtUserInitialize(0, 00000000, 00000000)
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/display.c:79)
err: InitDisplayDriver
(\Device\Video0, \Registry\Machine\System\CurrentControlSet\Hardware
Profiles\Current\System\CurrentControlSet\Services\VBE\Device0);
What happens here? It's a normal bootup, everyone should see this. Why
is invalid window station handle being passed, why do we need
NtUserInitialize to produce ERR debug print, along with
InitDisplayDriver. Are those errors? If not, then why the hell are they
being printed? If yes, then I don't see any info about actual errors.
6.
(/srv/buildbot_cmake/full_cmake/build/win32ss/user/ntuser/window.c:2416)
err: DestroyWindow AOW
AOW? ORLY?
7. MASSIVE portcls spam. I won't even count lines.
(/srv/buildbot_cmake/full_cmake/build/drivers/wdm/audio/backpln/portcls/undoc.cpp:281)
Calling Node 16 MajorTarget B01EF750 MinorTarget 00000000 PropertySet
{45ffaaa0-6e1b-11d0-bcf2-444553540000} PropertyId 4 PropertyFlags
10000200 InstanceSize 0 ValueSize 40 Handler FB24E58A PropertyRequest
FF55B5F8 PropertyItemFlags 203 PropertyItemId 4
A few pages of that stuff. Is it really useful for everyone, including
automated testing systems?
8. A work queue deadlock. Not a good thing at all
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/ex/work.c:351) EX: Work
Queue Deadlock detected: 1
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/ex/work.c:353) Dynamic
threads queued 2
9. ???
All that resulted from my desire to just compare logs attached to the
bug report. New log is totally unreadable, I had to spend time figuring
out where actually that Live Essentials app was started, what problems
it shows, etc.
Best regards,
Aleksey.
Hello,
I can see donations have slowed down too much.... so, reaching 30,000 €
goal seems ... quite impossible at the short-term...
So, i wanted to ask... what about hiring devs for months? i know its a
short period of time, but i feel ReactOS needs it ( and them, also,
speaking about devs) asap :)
Hi,
it appears that one of our servers has decided to definitely give up
today.
A temporary solution has been deployed to ensure ISOs are still stored
properly. But, as a side effect, for the moment:
- doxygen is not reachable any longer;
- cppcheck run is not reachable any longer;
- ISOs are not reachable any longer.
We're working to get this back as quick as possible.
Sorry for the inconvenience.
With my best regards,
Le samedi 02 juin 2012 à 04:04 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/876
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 56689
> Blamelist: jimtabor
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 31st of May, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. As usual, volunteers are welcome.
An agenda for the meeting is being worked on now and will be posted
later. Please email me your suggestions before the meeting so that the
resulting agenda could be compiled beforehand.
With the best regards,
Aleksey Bragin.
hi. I'm a software engineering student last semester. My final project is translation of an open source o/s to Persian( farsi ). i see reactos and download its source code and Introduce the project to svn buti cant build it. please help me or send some useful tutorials.
This was due to a short outage on our side.
Problem fixed and build re-queued.
Sorry for the inconvenience.
Le mercredi 23 mai 2012 à 20:25 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Debug/builds/838
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 56652
> Blamelist: jimtabor
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Hi,
we are currently experiencing a downtime on our storage network. We are
actively working to get this back as soon as possible.
As a side effect, SVN is currently in read-only to prevent any further
build to be lost.
We are sorry for the inconvenience.
With my best regards,
On Tue, 2012-05-15 at 12:51 +0000, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder Trunk_x86_GCCLin Release while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Trunk_x86_GCCLin%20Release/builds/73
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1B
>
> Build Reason: The Periodic scheduler named 'release' triggered this build
> Build Source Stamp: HEAD
> Blamelist:
>
> BUILD FAILED: failed shell
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Hello together!
Is it just me or did the complete thread "Feedback 0.3.14" (or so) on
the forum by another Sven (I don't remember his full username) disappear
from yesterday to today? Even in the "my posts" view my two posts that I
have done in that thread aren't listed. Also it seems that the youngest
"no working reinstall driver button" thread by naums disappeared as
well. They don't appear to have been moved (there is no reference to a
moved thread), but they are simply gone. Is this a known problem? Were
they somehow hidden?
Regards,
Sven
Runner-up to Arty's patch of the year.
Best regards,
Alex Ionescu
On Sun, Apr 29, 2012 at 3:00 AM, <tkreuzer(a)svn.reactos.org> wrote:
> Author: tkreuzer
> Date: Sat Apr 28 20:00:09 2012
> New Revision: 56442
>
> URL: http://svn.reactos.org/svn/reactos?rev=56442&view=rev
> Log:
> [PSEH]
> Fix a serious bug in PSEH that could lead to stack corruption and was causing CSRSS to crash, when large amounts of text were output on the console.
> Background: PSEH used __builtin_alloca to allocate an SEH registration frame on the stack on demand, ie only for the first try level. But there are some nasty things with __builtin_alloca: First it DOES NOT - as one might think - free the allocated memory, once the allocation "goes out of scope", like with local variables, but only on function exit. Therefore it cannot normally be used inside a loop. The trick that PSEH used to "fix" this problem, was to save the stack pointer and reset it back at the end. This is quite problematic, since the rest of the code might assume that the stack pointer is still where it was left off after the allocation. The other thing is that __builtin_alloca() can allocate the memory whenever it likes to. It can allocate everything on function entry or not allocate anything at all, when other stack variables that went out of scope have left enough space to be reused. In csrss it now happened that the allocation was done before the stack pointer was saved,
> so the memory could not be freed by restoring the old stack pointer value. That lead to slowly eating up the stack since the code was inside a loop.
> The allocation is now replaced with a variable sized array. The variable stays in scope until the _SEH2_END and will be automaticall cleaned up by the compiler. This also makes saving and restoring the stack pointer obsolete.
> Reliability++
>
> Modified:
> trunk/reactos/include/reactos/libs/pseh/pseh2.h
>
> Modified: trunk/reactos/include/reactos/libs/pseh/pseh2.h
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/include/reactos/libs/pseh/…
> ==============================================================================
> --- trunk/reactos/include/reactos/libs/pseh/pseh2.h [iso-8859-1] (original)
> +++ trunk/reactos/include/reactos/libs/pseh/pseh2.h [iso-8859-1] Sat Apr 28 20:00:09 2012
> @@ -192,7 +192,6 @@
> if(_SEHTopTryLevel) \
> { \
> _SEH2LeaveFrame(); \
> - __asm__ __volatile__("mov %0, %%esp" : : "g" (_SEHStackPointer)); \
> }
>
> #define __SEH_END_SCOPE_CHAIN \
> @@ -219,16 +218,14 @@
> static const int _SEH2ScopeKind = 0; \
> volatile _SEH2TryLevel_t _SEHTryLevel; \
> volatile _SEH2HandleTryLevel_t _SEHHandleTryLevel; \
> - void * _SEHStackPointer; \
> + _SEH2Frame_t _SEH2Frame[_SEHTopTryLevel ? 1 : 0]; \
> volatile _SEH2TryLevel_t * _SEH2TryLevelP; \
> _SEH2Frame_t * const _SEH2FrameP = _SEHTopTryLevel ? \
> - ({ __asm__ __volatile__("mov %%esp, %0" : "=g" (_SEHStackPointer)); __builtin_alloca(sizeof(_SEH2Frame_t)); }) : \
> - _SEHCurFrameP; \
> + _SEH2Frame : _SEHCurFrameP; \
> \
> (void)_SEH2ScopeKind; \
> (void)_SEHTryLevel; \
> (void)_SEHHandleTryLevel; \
> - (void)_SEHStackPointer; \
> (void)_SEH2FrameP; \
> (void)_SEH2TryLevelP; \
> \
>
>
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 26th of April, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. Volunteers welcome.
An agenda for the meeting will be posted when the meeting starts. Please
email me your suggestions before the meeting so that the resulting
agenda could be compiled beforehand.
With the best regards,
Aleksey Bragin.
April 2012 Meeting Minutes
2012-04-26
19:00 UTC
Fezile, #meeting
Proceedings
===========
* Meeting started at 19:20 UTC by Amine Khaldi.
* Point 1: The state of Trunk
-----------------------------
* Amine Khaldi mentioned that we still have several regressions to get
fixed. Olaf Siejka stressed the fact that developers should actually
look into these regressions and fix them, and wondered about the optimal
selection process to ensure this.
* Timo Kreuzer suggested that we should assign these regressions, to
increase the possibility of having them fixed. He explained that the
selection should be by the guilty revision first (the revision that
triggers the regression), and the author of that revision should at
least take a look, and if it's *really* not his fault and he can't fix
it, then he can assign it back to ros-bugs.
* Amine Khaldi mentioned that at the moment there is no way to know what
developers are working on exactly, until they commit, and suggested
using bug reports to document the development, so that commits will
mention them at the end.
* Amine also suggested the following process for the regressions: We
assign those regressions to the author of the guilty revision, the
developer investigates the regression. If he's able to fix the bug, he
changes the bug status to "Assigned" which means he now owns this bug.
If he can't fix it, he will document his finding so far (a comment in
the bug report) and he assigns the bug to any other developer that he
thinks he can fix this, and so on.
* Everyone agreed, as a result, that we should assign regressions, and
that developers should look at what's assigned to them.
* Point 2: Overview of the Atlassian tools
------------------------------------------
* Amine Khaldi gave an overview of what we plan to do with Atlassian
products (Jira, FishEye, Crucible, Bamboo..etc) in case people didn't go
to their website to read about them and watch their videos
(http://www.atlassian.com/).
* Olaf Siejka asked about an ETA for the Atlassian tools adoption.
Aleksey Bragin mentioned that this will happen in the coming two weeks.
* Point 3: Discussing a possible change in the release cycle
------------------------------------------------------------
* Alexander Rechitskiy presented some links from the KDE project about
their svn guidelines, commit policy, release schedule, minor point
releases...etc.
* After a lengthy discussion, the team decided to continue the already
started efforts to improve efficiency and minimize regressions (like
leveraging Patchbot, the recent major Testman improvements...etc).
* Meeting closed at 21:26 UTC by Amine Khaldi.
* Minutes written by Amine Khaldi.
> Author: tkreuzer
> [NTOSKRNL]
> Fix SepGet*FromDescriptor, returning NULL, when the relative offset is 0.
> Fixes VMware tools installer.
Someone buy that man a beer!
Hi guys,
I have compiled the whole project and just want to copy ntoskrnl. Here
is what I execute:
---------------------------------------------------------------------
D:\ReactOS\src\ReactOS-0.3.14-CLT2012>make ntoskrnl_install
[COPY] Z:\ReactOS\system32\ntoskrnl.exe
Total Build Time: 00:02:04
---------------------------------------------------------------------
I don't know why it takes more than 2 minutes. Is it correct?
Thanks.
Hi,
this year, the 6th of June will be once again a special day. This will
be the one, the Internet Society has chosen to launch IPv6:
http://www.worldipv6launch.org/. It means that starting with this day,
all the participant will enable IPv6 and provide it the days, months,
years after.
The ReactOS Foundation will take part in this event. Currently some
services and servers are already available in IPv6, but are not fully
maintained. Starting with the 6th of June, major ReactOS services and
servers will be available for everybody with IPv6. A roadmap for IPv6
deployment can be found on the ReactOS wiki at:
https://www.reactos.org/wiki/IPv6. You will be able to follow all the
progress with IPv6.
This means that after the 6th of June, any ReactOS developer will be
able to work with an IPv6 only on our infrastructure.
The transition will be done smoothly.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
I've posted a topic on the Forums to discuss the roadmap to 0.4.0 (whatever
it may be).
ReactOS has been on the 0.3.x branch for almost six years, and there's been
talk of 0.4, so I'd like to hear from any developers on what plans or goals
you might have for 0.4.0, whenever it comes out (within 1-2 years?) If you
don't currently have any concrete goals or plans (which I've heard is a
possibility), then perhaps it would be a good time to start a dialog
between developers and the community so we can start to get an idea of what
your (ReactOS) expectations are, and what's in store.
http://www.reactos.org/forum/viewtopic.php?f=2&t=11114
It could also give you something to point people to when people ask about
0.4.
02.04.2012 0:42, akhaldi(a)svn.reactos.org пишет:
> Author: akhaldi
> Date: Sun Apr 1 20:42:43 2012
> New Revision: 56311
>
> URL: http://svn.reactos.org/svn/reactos?rev=56311&view=rev
> Log:
> * Discussing it will only waste time, so we better have it then talk about it after.
I was thinking it's some of my old commits, until I read the line about
april fools day :)
> * I'm just kidding, you know, April's fool and all ;)
>
WBR,
Aleksey.
That was a nice catch!
07.04.2012 0:13, sginsberg(a)svn.reactos.org пишет:
> Author: sginsberg
> Date: Fri Apr 6 20:13:33 2012
> New Revision: 56333
>
> URL: http://svn.reactos.org/svn/reactos?rev=56333&view=rev
> Log:
> - Even while I love having the trap/fpu/context code in C, the bugs this switch introduced continue to amaze me. This time, fix a bug from 45156 when KiFlushNPXState was rewritten in C. The C version could miss to restore the interrupt state, which would lead to interrupts being disabled when it was not expected. This "interrupt leak" was seen in the page fault handler if a page fault occurred after interrupts had been disabled (which had sometimes been observed to occur on the test server during exception handling and thread creation when KiFlushNPXState had been called). This didn't completely hang the system because during thread creation (and other system calls where this may have happened) interrupts would be re-enabled when returning to user mode when restoring eflags, and the exception handling would result in a system call which would enable interrupts again (it appears exception handler would have run with interrupts disabled, though!). This is now fixed, as well as any other issues this might have caused. The hack in the page fault handler remains until another issue has been fixed.
>
> Modified:
> trunk/reactos/ntoskrnl/ke/i386/cpu.c
>
> Modified: trunk/reactos/ntoskrnl/ke/i386/cpu.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ke/i386/cpu.c?rev…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ke/i386/cpu.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ke/i386/cpu.c [iso-8859-1] Fri Apr 6 20:13:33 2012
> @@ -1323,7 +1323,12 @@
> if (Thread->NpxState != NPX_STATE_LOADED)
> {
> /* If there's nothing to load, quit */
> - if (!SaveArea) return;
> + if (!SaveArea)
> + {
> + /* Restore interrupt state and return */
> + __writeeflags(EFlags);
> + return;
> + }
>
> /* Need FXSR support for this */
> ASSERT(KeI386FxsrPresent == TRUE);
>
>
March 2012 Meeting Minutes
2012-03-29
19:00 UTC
Fezile, #meeting
Proceedings
===========
* Meeting started at 19:00 UTC by Aleksey Bragin.
* Point 1: The state of Trunk
-----------------------------
* Cameron Gutman gave some examples how badly Trunk has regressed since
0.3.14:
- Frequent bugchecks and assertions in the console
- Broken Unicode in the console
- Several key apps such as Firefox, Ping, Dwnl and Notepad being
broken or rarely working
He opened a discussion about improving the quality of Trunk.
* Timo Kreuzer favorized a stricter revert-on-regressions policy. By
employing the Patchbot buildslave, "evil" changes should be detected in
advance before committing them. According to Giannis Adamopoulos, the
Patchbot currently needs 20 minutes in total for building and testing a
patch.
* Colin Finck asked whether the current regressions were visible in the
automated regression tests. Aleksey Bragin denied this for most of them
as these were usability problems not detected by our regression tests.
* Various people suggested frameworks such as AutoIt and AutoHotKey to
automate application testing as well.
* To also automate real hardware testing, Jan Blomqvist Kinander has set
up another server. He reported that he could successfully perform a
remote ReactOS installation on it and just needs some scripts to
automate the procedures now.
* Aleksey Bragin illustrated his plan to move more towards loosely
managed development. In particular, he wants to introduce Atlassian
tools such as FishEye and JIRA to plan activity and actually do stuff.
* Cameron Gutman wanted a firm decision about dealing with regressions
first. Aleksey Bragin responded that the current rules still apply: A
commit shall be reverted after one day if it breaks booting or
installation. Other regressions shall be reported in Bugzilla using the
REGRESSION prefix.
* Olaf Siejka criticized the way bugs are currently handled. The list at
http://www.reactos.org/wiki/Bug_Filters#Patch_review_list is getting
bigger and bigger while developers don't take responsibility for it. He
added that a decision was taken to release early last month, although no
progress towards implementing it was visible.
* Alex Ionescu joined the meeting later and reopened the discussion
about using Atlassian tools. In his opinion, JIRA and FishEye can
support our development along with Bamboo as a build and continuous
integration system. Later on, these systems could be set up to only
accept a commit if it can be successfully built by Bamboo.
- Olaf Siejka wants to set up a Bamboo test system to evaluate the
tool.
- Alex Ionescu will send out an E-Mail as soon as our setup is ready
for testing.
* Point 2: Plan for the next month
----------------------------------
* The previous discussion about improving development using new tools
continued here. While Aleksey Bragin outlined that he wants to finish
the setup in April, Alex Ionescu gave more examples about what needs to
be changed when moving to JIRA:
- A dynamic component maintainer list should be added to establish
a clear chain of responsibility for all parts of ReactOS.
- User privileges should be changed to let only component maintainers
classify their bugs.
* Furthermore, the list at
http://www.reactos.org/wiki/Bug_Filters#Patch_review_list has been
discussed again. Alex Ionescu and Timo Kreuzer agreed that such general
lists are pointless and the following approach was suggested instead:
- Developers owning bugs and being mailed about them
- Release not being made until all important bugs are fixed
- Someone to prioritize which bugs are blocking a release
* Alex Ionescu outlined more ideas about improving the release process.
He suggested to create a roadmap for each release and picking several
specific bugs as goals for this release. Only fixes for these bugs
should go into a release, new features could be prepared in branches.
* The branches idea was picked up by Amine Khaldi who questioned that
SVN was able to properly handle more branches for new features, release
preparation, etc. due to its limited branching capabilities.
* Alex Ionescu did not agree with this, because people can merge just
subdirectories of a branch into Trunk or even bundle all changes in
.patch files and simply apply them.
* Timo Kreuzer called for a feature freeze in Trunk before the
discussion on point 2 ended, but Aleksey Bragin stated that this would
prevent further work on fixing Mm.
* Aleksey Bragin finally repeated that he is going to finish the setup
of the new tools in April and wants to get everybody used to them. The
idea of having modules owners shall get more developer responsibility
towards issues and patches.
* Point 3: Next release discussion
----------------------------------
* Aleksey Bragin postponed this discussion to the next meeting as most
of the topics have already been covered in the discussion about Trunk.
No objections were raised.
* Point 4: New website status
-----------------------------
* Maciej Bialas reported that he is at the point of applying small fixes
now as well as importing the user database into Drupal. He stated that
every user needs to change his password after the migration because of
different hashing algorithms used in Drupal and RosCMS.
* Pierre Schweitzer noted that we should prevent another mass mailing of
all registered users due to the problems caused by the last one.
* Ziliang Guo proposed to just create a sticky forum post and write a
mail to a ReactOS mailing list about the password changes. There were no
objections.
* The participants agreed to continue discussions about website content
on the mailing lists.
* Point 5: Miscellaneous
------------------------
* Giannis Adamopoulos picked up the new subsystem layout for Win32k,
which had already been discussed a year ago and was postponed. He
outlined it at http://pastie.org/3694259. Aleksey Bragin, James Tabor
and Timo Kreuzer agreed on it, so it will be committed within the next 4
days.
* Art Yerkes reported about his work on NewCC. In particular, he is
currently looking at a bug not existing in a non-NewCC build. He expects
other issues afterwards, but thinks that the entire work is progressing
well.
* Meeting closed at 21:55 UTC by Aleksey Bragin.
* Minutes written by Colin Finck.
All Facebook fanpages will be to switch to the new timeline layout this
weekend. This means we need a cover picture for our reactos fan page.
If artistic guys out there wanna put something together, we'll upload it to
our fanpage.
Maybe someone could start a thread in the forum to gather some interest?
Cheers,
Ged.
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 29th of March, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. Volunteers welcome.
Proposed agenda will be posted to this list tomorrow. Please email me
your suggestions.
With the best regards,
Aleksey Bragin.
Hello dear React OS mailing list!
I've found that ReactOS dbghelp.dll includes PDB file parser. Does anyone
know where I can find documentation of PDB internal structure?
Thanks,
Svyatoslav Kuzmich
Am 19.03.2012 17:21, schrieb tfaber(a)svn.reactos.org:
> }
> }
> - uState = uState;
> + this->uState = uState;
> TRACE("--\n");
> }
LOL!
Thats another reason why I love C++, it makes people write very funny
code :D
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
On 08.03.2012 2:27, jgardou(a)svn.reactos.org wrote:
> Author: jgardou
> Date: Wed Mar 7 22:27:48 2012
> New Revision: 56083
>
> URL: http://svn.reactos.org/svn/reactos?rev=56083&view=rev
> Log:
> Branch for C++.
> Amine will be proud.
>
Me too ;)
One last bug squashed (hopefully) - now testbot should detect missing ISO and break up runtime at prepare stage.
On Wed, Mar 7, 2012, at 11:30 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/5220
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: The web-page 'rebuild' button was pressed by 'osiejka':
>
> Build Source Stamp: 56072
> Blamelist:
>
> BUILD FAILED: failed Initial preparations
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr
[NTOSKRNL]
- Fix the unload path
- This does expose some bugs: 2 cont-able assertions in ARM3 after
unplugging a USB storage device (during usbstor unload), HID unload doesn't
seem to work correctly (somebody still has references to the devices), other
issues may pop up too
I've tracked this issue down to using loader heap to allocate the LDR data
entry (which gets freed by the kernel during init). This makes it invalid
when we go to read the module object when we unload it, causing a crash. I'm
not sure how to move forward from here but the changes needed are in
FreeLoader's peloader.c. After fixing that, I'm running into another issue
where it appears that LdrEntry->LoadedImports is no longer valid (set for
boot drivers during kernel init) so it results in a null pointer
dereference. I've confirmed that this crash only occurs when boot loaded
drivers are unloaded; any other PnP driver loaded after boot unloads
perfectly.
Richard (or someone else knowledgeable in the area), if you could take a few
minutes to figure this out for me that would be fantastic.
Here is the log and backtrace after I fixed the LDR data entry allocation
type:
(C:\Users\Cam\reactos\trunk\ntoskrnl\io\iomgr\device.c:447) Unloading driver
'\Driver\usbstor' (automatic)
(C:\Users\Cam\reactos\trunk\ntoskrnl\io\iomgr\driver.c:61) Deleting driver
object '\Driver\usbstor'
(C:\Users\Cam\reactos\trunk\ntoskrnl\mm\ARM3\sysldr.c:935) Leaking driver:
usbstor.sys
Entered debugger on first-chance exception (Exception Code: 0xc0000005)
(Page Fault)
Memory at 0x00000000 could not be read: Page not present.
kdb:> bt
Eip:
<NTOSKRNL.EXE:b0c71 (ReactOS/ntoskrnl/mm/ARM3/sysldr.c:389
(MiDereferenceImports@4))>
Frames:
<NTOSKRNL.EXE:b0a7f (ReactOS/ntoskrnl/mm/ARM3/sysldr.c:947
(MmUnloadSystemImage@4))>
<NTOSKRNL.EXE:5ce2c (ReactOS/ntoskrnl/io/iomgr/driver.c:80
(IopDeleteDriver@4))>
<NTOSKRNL.EXE:d63f5 (ReactOS/ntoskrnl/ob/oblife.c:211 (ObpDeleteObject@8))>
<NTOSKRNL.EXE:da790 (ReactOS/ntoskrnl/ob/obref.c:237
(@ObfDereferenceObject@4))>
<NTOSKRNL.EXE:59c24 (ReactOS/ntoskrnl/io/iomgr/device.c:61
(IopDeleteDevice@4))>
<NTOSKRNL.EXE:d63f5 (ReactOS/ntoskrnl/ob/oblife.c:211 (ObpDeleteObject@8))>
<NTOSKRNL.EXE:da790 (ReactOS/ntoskrnl/ob/obref.c:237
(@ObfDereferenceObject@4))>
<NTOSKRNL.EXE:73adc (ReactOS/ntoskrnl/io/pnpmgr/pnpmgr.c:1286
(IopSynchronousCall@12))>
<NTOSKRNL.EXE:73b23 (ReactOS/ntoskrnl/io/pnpmgr/pnpmgr.c:585
(IopSendRemoveDevice@4))>
<NTOSKRNL.EXE:7532a (ReactOS/ntoskrnl/io/pnpmgr/pnpmgr.c:2214
(IopEnumerateDevice))>
<NTOSKRNL.EXE:7550c (ReactOS/ntoskrnl/io/pnpmgr/pnpmgr.c:4672
(IoSynchronousInvalidateDeviceRelations@8))>
<NTOSKRNL.EXE:75530 (ReactOS/ntoskrnl/io/pnpmgr/pnpmgr.c:889
(IopAsynchronousInvalidateDeviceRelations@8))>
<NTOSKRNL.EXE:6a737 (ReactOS/ntoskrnl/io/iomgr/iowork.c:27
(IopWorkItemCallback@4))>
<NTOSKRNL.EXE:42056 (ReactOS/ntoskrnl/ex/work.c:162
(ExpWorkerThreadEntryPoint@4))>
<NTOSKRNL.EXE:efaca (ReactOS/ntoskrnl/ps/thread.c:156
(PspSystemThreadStartup@8))>
<NTOSKRNL.EXE:100d63 (ReactOS/ntoskrnl/ke/i386/thrdini.c:78
(KiThreadStartup@0))>
<NTOSKRNL.EXE:efa66 (ReactOS/ntoskrnl/ps/thread.c:625
(PsCreateSystemThread@28))>
Regards,
Cameron
After a quick look into your problems with patchbot it seems that vbox scripts were missing some errorlevel checks, which should bail out the test run at prepare stage when ISO was not present (which is the situation when you dont pass the proper revision/id number. Same thing was with newcc1 tests. I added some debug prints so if my current solution wont do its job, i`ll at least know bit more about the problem.
By that occasion i found out a problem with current ROSBE - its not emitting proper ERRORLEVEL at the end of the build, due to tee/buildtime/flash/sound playback or any of similar crap that is getting the final ERRORLEVEL value. For main building step i hacked around this issue by simply checking for ISO file at the end and erroring out if its not there. For host building part, this is more complicated. I tried removing the stuff mentioned above, but it still doesnt work. Dreimer: it would be of help if you could fix this problem.
--
With best regards
Caemyr
Sorry for the error spam, had to fix one erroneous check (that forced exiting with errorlevel 0 instead of the proper one).
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Date: Tue, 06 Mar 2012 21:18:43 +0000
Subject: buildbot failure in ReactOS on Windows_AMD64_1 VBox-Test
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/5204
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_2
Build Reason: The web-page 'rebuild' button was pressed by 'osiejka':
Build Source Stamp: 56063
Blamelist: cgutman
BUILD FAILED: failed Initial preparations
sincerely,
-The Buildbot
--
With best regards
Caemyr
Hi,
release builds will finally be available again. Those will be daily
built against most recent head. They will be findable at usual place.
For the moment, no new release build is available since release build
its broken (cf:
http://build.reactos.org/builders/Trunk_x86_GCCLin%20Release/builds/1/steps…).
With my best regards,
--
Pierre Schweitzer<pierre(a)reactos.org>
System Administrator
ReactOS Foundation
Nice try!
However it failed on KVM:
http://build.reactos.org/builders/Linux_AMD64_1%
20KVM-CMake-Test/builds/255/steps/test/logs/stdio
Regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Could it be a ccache miss?
Failed to read source file: 0
mingw32-make.exe[3]: *** [boot/freeldr/freeldr/frldr16.bin] Error -4
[ 98%] [ 98%] mingw32-make.exe[2]: *** [boot/freeldr/freeldr/CMakeFiles/freeldr.dir/all] Error 2
mingw32-make.exe[2]: *** Waiting for unfinished jobs....
----- Original message -----
From: buildbot(a)reactos.org
To: caemyr(a)myopera.com
Date: Sun, 04 Mar 2012 20:03:52 +0000
Subject: buildbot failure in ReactOS on CMake_x86_GCCWin Debug
The Buildbot has finished a build on builder CMake_x86_GCCWin Debug while building ReactOS.
Full details are available at:
http://build.reactos.org/builders/CMake_x86_GCCWin%20Debug/builds/2966
Buildbot URL: http://build.reactos.org/
Buildslave for this Build: Windows_AMD64_1
Build Reason: scheduler
Build Source Stamp: 56010
Blamelist: sir_richard
BUILD FAILED: failed building bootcd
sincerely,
-The Buildbot
--
With best regards
Caemyr
Hi,
this revision actually fixed KVM testbot (ie r55980 was not mandatory).
But this has been hidden by two things:
- sysreg regression: this has been kicked out by now;
- trunk regression: introduced by r55977, it is still present. And
results couldn't be sent to testman since rosautotest got messed up and
ran same tests several times;
Sorry for the issues caused by sysreg regression.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Cabman error, build was restarted and went fine
On Sat, Mar 3, 2012, at 08:26 PM, buildbot(a)reactos.org wrote:
> 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/596
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_1a
>
> Build Reason: scheduler
> Build Source Stamp: 55970
> Blamelist: tkreuzer
>
> BUILD FAILED: failed building bootcd
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr
This is due to an issue within both ReactOS and sysreg.
ReactOS appears not to boot any longer with r55879 on KVM, and crashing
during ntoskrnl init on CD.
Sysreg is also not catching the crash, nor hitting the timeout and so is
not killing the VM. And then, buildbot is unable to start any new test
due to the frozen VM.
I have killed the frozen VM and restarted HEAD (ie, r55886 testing). If
the fix has been really committed with r55880, it should work properly.
Will investigate the issue ASAP, to ensure it doesn't happen any more.
Le lundi 27 février 2012 à 17:40 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Linux_AMD64_1 KVM-CMake-Test while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/Linux_AMD64_1%20KVM-CMake-Test/builds/76
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: Triggerable(Linux_AMD64_1 KVM-CMake-Test Trigger)
> Build Source Stamp: 55886
> Blamelist: ion
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Cabman failure. Repeated.
On Fri, Mar 2, 2012, at 10:24 PM, buildbot(a)reactos.org wrote:
> 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/566
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_1a
>
> Build Reason: scheduler
> Build Source Stamp: 55939
> Blamelist: khornicek
>
> BUILD FAILED: failed building bootcd
>
> sincerely,
> -The Buildbot
>
--
With best regards
Caemyr
I was wondering why the Cmake results are different between the
Windows/ReactOS and Unix/Linux platforms. The compressed trunk CD images
available for download differ by about 6MB.
Expecting identical output (checksums, file sizes) on different
platforms even with the same compiler isn't realistic ofcourse but above
mentioned 6MB is a bit much.
Creating dbgwin-builds makes sense, but if the Unix builder builds
faster and smaller builds, and makes them earlier available for
download, what's the point in making the Windows build available
publicly? Would it make more sense to offer MSVC builds if
license-technical allowed? Or automated builds of CLT-type (combined
installCD + liveCD) ?
Bernd
It looks like the model B boards are now in manufacture.
http://www.raspberrypi.org/archives/509
There are only 10k being made being made in this batch and demand is really
high, so I doubt they'll last longer than a few minutes.
With only 256MB RAM available, I doubt Windows 8 will ever run on it
although Windows Embedded Compact 7 might.
I know the reactos arm port is still a way off, but this could be a golden
opportunity for reactos.
At $25 per computer, they're gonna sell hundreds of thousands of these
things and most buyers will be enthusiasts/developers.
Ged.
Hi,
to address an increasing ReactOS developers demand, you'll be able to
find regtest CDs used by KVM testbot at the URL:
http://iso.reactos.org/regtestcd/
I think I'll probably put the KVM testbot machine specifications on the
wiki to help as well.
Regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
This is due to the new way test CDs are handled on the builder. I'm on
it to get it back to working state.
Le mardi 28 février 2012 à 22:22 +0000, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder CMake_x86_GCCLin Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/CMake_x86_GCCLin%20Debug/builds/96
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Linux_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 55909
> Blamelist: janderwald
>
> BUILD FAILED: failed compile_5
>
> sincerely,
> -The Buildbot
>
>
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
February 2012 Meeting Minutes
2012-02-23
19:45 UTC
Fezile, #meeting
Proceedings
===========
* Meeting started at 19:45 UTC by Aleksey Bragin.
* Point 1: Release status: 0.3.15
---------------------------------
* Aleksey Bragin proposed that we prepare trunk and release 0.3.15, as
it is now, before anything major happens. Several members then wondered
about the status of USB and the "mshtml bug". Jerome Gardou explained a
bit about how the mshtml bug is far from completely being fixed, because
if you look at testbot's results, there are still some problems with
ASSERTs hit and some bad pagefaults happening when paging out.
* A lengthy discussion occurred, about how ready trunk is, whether it's
in a better state than 0.3.14, the state of the theme to be bundled with
ros, the plan for CLT, whether we should go 0.4<something> or 0.3.15...
This was settled through a voting: "Do you agree to release 0.3.15 with
current trunk features, before CLT?".
* The total number of votes was 21, with 11 votes as Yes, 5 as No, and 5
abstentions. As a result, we will be having a 0.3.15 release with CLT
being the deadline.
* Point 2: New website status and migration plans
-------------------------------------------------
* Amine Khaldi gave a quick summary on the state of the website revamp:
- Quite some progress has been made in the theming department, and
it's visible from the playground. It's starting to look a lot like the
current one, which means it's almost done (only some issues are left).
- Maciej Bialas has been investigating how to import users from the
RosCMS. We will most likely need to compromise: members will have to
reenter passwords when we migrate, but we'll see.
- Amine Khaldi then mentioned that we need help from web devs
familiar with Drupal. Alexander Rechitskiy mentioned that he has a guy
that wants to be part of the web team, and he passes his info to Amine
to establish the contact.
- He also mentioned that Maciej is very busy, so the progress will
slow down, and that the current short term plan is to continue the
theming work, provide a way to import users, import the rest of data
from wiki/bugzilla...etc and finally add the phpbb bridge.
* He then summarized the summary by saying: We needs skillful drupal
guys, we're almost there, and that's it.
* Point 3: CMake migration and finally abandoning RBuild
--------------------------------------------------------
* Amine Khaldi suggested that it's time to ditch rbuild, as he suspects
most of our members have migrated already. Agreement on that, from ours
members, was unprecedented as *everyone* were on favor of this :)
* We agreed on doing the necessary commits/infrastructure changes ASAP,
ie "tonight" (relative to the meeting of course), but that didn't happen
just yet so it's just a matter of time. Amine Khaldi wants to do the
honors (the commit that will remove rbuild and its related files).
* Amine Khaldi also mentioned that he's preparing a nice little surprise
for major build performance boost, on many levels, so stay tuned guys ;)
* Jerome Gardou explained that he'll be handling the PCH support to get
it to a much better state than it is right now.
* Point 4: Added per Amine Khaldi's request: GSoC preparations
--------------------------------------------------------------
* Amine Khaldi explained that he created a Google Doc and invited the
interested members. He asked the members to collaborate and shape up an
excellent ideas list, projects that fit in GSoC at both the time and
complexity levels.
* Colin suggested building up on the last year in terms of informative
content (wiki pages from last year), covering questions about how we
deal with students, our application form... etc.
* Meeting closed at 21:45 UTC by Aleksey Bragin.
* Minutes written by Amine Khaldi.
> [USER32]
> Correct user32 japanese translation (and fix build as well)
For the record, this doesn't fix build because:
1) It was not broken (hint: r55860).
2) The module that broke build back then was shell32, not user32.
Regards,
Amine.
0x19 bugcheck with CM corruption. Test reran.
On Wed, Feb 22, 2012, at 10:30 PM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed 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/4897
>
> 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: 55816
> Blamelist: sginsberg
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of this month, 23rd of February, 19:00 UTC.
The meeting will be at irc://fezile.reactos.org (Port 6667, no SSL) in
the channel #meeting. Note that the IRC service will only be started
shortly before the meeting. Your participation passwords will be emailed
to you shortly before the meeting starts.
If someone still is not getting passwords sent before a meeting - please
email Colin or Pierre before the meeting started to get one.
In order to save time, let's choose who is going to be the minute taker
on the upcoming meeting. Volunteers welcome.
Proposed agenda for the meeting:
1. Release status: 0.3.15
2. New website status and migration plans.
3. CMake migration and finally abandoning RBuild.
4. 0.3.14 release party.
More suggestions are welcome as usual.
With the best regards,
Aleksey Bragin.
i changed email to this one microsoft windows live is better than google.
now i saved the best part for last, go her for a list of win32 api functions:
http://j00ru.vexillium.org/w32k_syscalls/
it will help a lot in the development of reactos and make a lot mor programs run on then system
2nd stage pool corruption at the end, CM assert at subsequent reboots. I restarted the test and it worked fine the second time.
On Wed, Feb 22, 2012, at 05:28 PM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed 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/4888
>
> 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: 55808
> Blamelist: sginsberg
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
VBox was locked up. Usurp: could you look into it? VBox window is stuck with Stopping status. Perhaps sysreg should kill the whole process and restart it, just to be safe?
Best regards
On Wed, Feb 22, 2012, at 12:15 PM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed 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/4882
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_2
>
> Build Reason: The web-page 'force build' button was pressed by 'osiejka':
>
> Build Source Stamp: 55804
> Blamelist:
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
Le 21/02/2012 01:32, jgardou(a)svn.reactos.org a écrit :
> Author: jgardou
> Date: Tue Feb 21 00:32:24 2012
> New Revision: 55770
>
> URL: http://svn.reactos.org/svn/reactos?rev=55770&view=rev
> Log:
> [NTOSKRNL/MM]
> - finally, release user shared data at process address space cleanup.
> - release PDE pages that might not be freed at process end.
> - Let the caller handle PDE release when deleting a PTE
> - restore Richard's ASSERT : All user PDE pages are now freed!
Addendum to log :
When a page maps a Prototype PTE, we can't know if it must be
deleted before dropping shared reference. Modify ASSERT accordingly.
Restore the ASSERTion that only page fault should provocate the
creation of the PDE and modify PDE refcounting in pageout code accordingly.
Bad pool bugcheck at 3rd stage boot, repeatable at subsequent restarts. Doesn't seem to be present when i issued retesting of that rev.
Regards
On Wed, Feb 22, 2012, at 12:44 AM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed 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/4876
>
> 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: 55800
> Blamelist: jgardou
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
VBox window hanged hard, at STOPPING. Sysreg could not restart it. Nothing happened even after vbox process being killed.
----- Original message -----
From: buildbot(a)reactos.org
To: ros-builds(a)reactos.org
Date: Tue, 21 Feb 2012 11:31:15 +0000
Subject: [ros-builds] Windows_AMD64_1 VBox-Test: build failed
The Buildbot has detected a failed 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/4844
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: 55770
Blamelist: jgardou
BUILD FAILED: failed test
sincerely,
-The Buildbot
--
With best regards
Caemyr
Yet another CM fsckup:
*** Fatal System Error: 0x00000019
(0x00000005,0xE11FF880,0x000000F0,0xE11FF798)
at end of 2nd stage. At subsequent reboots:
Assertion 'KeyCell->Signature == CM_KEY_NODE_SIGNATURE' failed at P:\Trunk_slave\x86_CMake\build\lib\cmlib\cminit.c line 115
We really need something to fight the pool corruptions, Aleksiej.
Testing will be restarted.
Best regards
On Tue, Feb 21, 2012, at 11:50 AM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed 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/4845
>
> 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: 55771
> Blamelist: jgardou
>
> BUILD FAILED: failed test
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
Another ghost:
[100%] Building C object drivers/wdm/audio/sysaudio/CMakeFiles/sysaudio.dir/dispatcher.c.obj
Failed to read source file: 0
mingw32-make.exe[3]: *** [boot/freeldr/freeldr/frldr16.bin] Error -4
mingw32-make.exe[2]: *** [boot/freeldr/freeldr/CMakeFiles/freeldr.dir/all] Error 2
mingw32-make.exe[2]: *** Waiting for unfinished jobs....
On Tue, Feb 21, 2012, at 11:36 AM, buildbot(a)reactos.org wrote:
> The Buildbot has detected a failed build on builder CMake_x86_GCCWin
> Debug while building ReactOS.
> Full details are available at:
> http://build.reactos.org/builders/CMake_x86_GCCWin%20Debug/builds/2729
>
> Buildbot URL: http://build.reactos.org/
>
> Buildslave for this Build: Windows_AMD64_1
>
> Build Reason: scheduler
> Build Source Stamp: 55775
> Blamelist: janderwald
>
> BUILD FAILED: failed building bootcd
>
> sincerely,
> -The Buildbot
>
>
>
--
With best regards
Caemyr
1. Time machines have not been invented so that's impossible.
2. I don't live in the past so that was stupid
3. I have my date/time done perfectly fine.
So next time don't say that to someone knows what they are talking about
I am planning on running because my school pc has 1.72gb of ram but I can't put a new os on physicle disk my parents will get very mad if I install os but not if I run it on cd.
Oh bye I have to go to bed in 6 minutes
I have taken into account the stuff you all sent about system specs since the pc will be mine at the end of my school year I am saving up for:
8gb of ram.
Some new hdds of over 80gb
I don't know how to add a new cpu, and they are very expensive.
Mikey
P.s.
Will a .iso work to make a live cd or usb boot cd,
I know I can do it with linux distros but not ReactOS.
Hello I am new here what are the system minimum specs as I have old system for development.
My dad says I get the old system at the ent of my school if I get good grades it has ubuntu 11.10 but it is slow I like to call it u-slow-os 1.6.
Epic.
On 16.02.2012 15:16, jgardou(a)svn.reactos.org wrote:
> Author: jgardou
> Date: Thu Feb 16 11:16:10 2012
> New Revision: 55631
>
> URL: http://svn.reactos.org/svn/reactos?rev=55631&view=rev
> Log:
> [NTOSKRNL/MM]
> - use ARM3 allocation for PDE pages.
> There is now one table for system PDEs, and their pages are not leaked anymore.
> Also fix bug 5857 (aka mshtml bug).
> Only for x86 now. Timo, I think you should do it for amd64 as well.
> Thanks for your patience, go back to testing now.
> A huge congrats to Cameron and Thomas, without them I wouldn't even have dared touching this code.
>
> Modified:
> trunk/reactos/ntoskrnl/mm/ARM3/virtual.c
> trunk/reactos/ntoskrnl/mm/i386/page.c
>
Hi,
due to popular request, a new ML is available (for read-only):
ros-builds. This ML will receive notifications sent by buildbot in case
of build breakge/tests breakage.
More notifications should be added any time soon.
For subscription, just go here:
http://reactos.org/mailman/listinfo/ros-builds
Regards,
Pierre
Hello,
during recent discussion, a topic about mailing lists appeared.
According to Pierre, we have 6 totally unused mailing lists, which are:
ros-cis
ros-errors
ros-kernel
ros-svn-diffs
ros-translate
ros-foundation
I propose to delete all those, maybe except for ros-foundation.
Any opinions?
WBR,
Aleksey Bragin.
Historical commit, deserving a nice rev number too!
(hmm, 69 maybe viewed by some as nice too, but better let's focus on the
"555" part ;))
On 12.02.2012 22:34, cgutman(a)svn.reactos.org wrote:
> Author: cgutman
> Date: Sun Feb 12 18:34:05 2012
> New Revision: 55569
>
> URL: http://svn.reactos.org/svn/reactos?rev=55569&view=rev
> Log:
> [USBDRV]
> - Terminate the NT4 USB driver
>
> Removed:
> trunk/reactos/drivers/usb/nt4compat/
>
>
Hi,
as requested I added a blacklisting ability to testman. The purpose of
this is to have some meaningful comparison between test runs without
completely disabling randomly behaving test sets. This means that
blacklisted test are still being run, logged and included in the Totals
summary. They won't affect the newly added "nonblacklisted summary"
only. The last thing needed before we can actually benefit from this is
to go through the tests, find those that give random results and either
fix them or add them to the blacklist. Please use this wiki page
http://www.reactos.org/wiki/Testman_blacklist to forge the list. Anyone
with web repo commit access (that includes me) can then update the
config itself.
WBR,
Kamil
Hi,
ok... last but not least, RosBE for Windows Version 2.0 is out too.
This is one of the last steps to the upcoming cmake switch with dumping rbuild fully and forever.
The setup files can be found here:
http://www.reactos.org/wiki/Build_Environment
Setup is the same good known NSIS based one for now. Just remove the old BE and let it install it over.
CMAKE usage instructions are here:http://reactos.org/wiki/CMake
Big thanks for this release goes to Heis and Colin from the Unix BE team, Amine for not killing me taking so long for a release and dralnix and blight_ for doing the first steps to a advanced BE years ago. Miss you, guys ^^
As for Unix one, I fully dump the support for any earlier Version of RosBE Windows starting from NOW.
Best regards,
Daniel
Hi,
finally, we are getting closer and closer to CMake switch. RosBE-2.0
release brings supports for CMake and all the changes made in the tool
chain. You can find it here:
https://sourceforge.net/projects/reactos/files/RosBE-Unix/2.0/
To install it, simply extract the tar.bz2, and then run the
RosBE-Builder.sh script.
For instructions about how to use CMake in ReactOS, have a look to that
wiki page: http://reactos.org/wiki/CMake
Regarding this release, I would like to thank Colin Finck who did
everything for it, but who have been obliged to let me release his work
due to his busy life.
RosBE 1.5 is not supported any longer.
And I invite everyone to switch to CMake (with RosBE2.0 Windows/Linux).
Rbuild deletion is now a matter of days.
The countdown for Rbuild deletion has started.
Regards,
Pierre
I must say, hpoussin proposed to get rid of bget in favor of rtl/heap.c,
and I criticized his idea because I had no trust in the old heap code.
Would reusing the new code be an option? Or you already invented the
"mini-heap" which works good enough?
WBR,
Aleksey.
On 10.02.2012 0:01, tkreuzer(a)svn.reactos.org wrote:
> Author: tkreuzer
> Date: Thu Feb 9 20:01:10 2012
> New Revision: 55518
>
> URL: http://svn.reactos.org/svn/reactos?rev=55518&view=rev
> Log:
> [FREELDR]
> - Enable new heap code and cleanup the heap, releasing unused memory, before starting reactos
> - Gives our kernel about 4MB additional memory, which - at the current leak rate - means around 8 minutes longer before it runs out of memory :)
> - Using the temp heap for all temporary allocations should increase the amount of saved space
>
> Removed:
> trunk/reactos/boot/freeldr/freeldr/mm/heap.c
> trunk/reactos/boot/freeldr/freeldr/rtl/bget.c
>
Hi all,
The Google Summer of Code 2012 project registration phase is starting in
three weeks.
Are we going to apply again after our success last year?
Who will be available as administrators and mentors?
Is anybody already collecting task ideas?
Cheers,
Colin
Le 06/02/2012 07:50, janderwald(a)svn.reactos.org a écrit :
>
> +if(ARCH MATCHES i386)
> + add_target_compile_flags(disk "-mrtd -fno-builtin -Wno-unused-variable -Wno-pointer-sign")
> +endif()
> +
>
Hey!
Those look very GCC centric. The corresponding flag for MSVC to -mrtd
would be /Gz. As for other flags, I'm unsure of what -fno-builtin would
correspond to, and others are only for warnings.
Cheers.
Jérôme.