Ros-dev

ros-dev@reactos.org

5790 discussions

Start a nNew thread

http://j00ru.vexillium.org/ntapi/
by mikey sibert 23 Feb '12

23 Feb '12

go here it might work i don't know it all runs on my pc.

1 0

system call list
by mikey sibert 23 Feb '12

23 Feb '12

can you send i list of the ones you have implemented

1 0

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

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

1 0

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

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

1 0

Re: [ros-dev] [ros-diffs] [jgardou] 55770: [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 ...
by Jérôme Gardou 22 Feb '12

22 Feb '12

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.

2 1

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

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

1 0

Fwd: [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 22 Feb '12

22 Feb '12

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

2 1

Re: [ros-dev] [ros-builds] Windows_AMD64_1 VBox-Test: build failed
by caemyr＠myopera.com 21 Feb '12

21 Feb '12

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

2 1

Re: [ros-dev] [ros-builds] CMake_x86_GCCWin Debug: build failed
by caemyr＠myopera.com 21 Feb '12

21 Feb '12

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 0

new
by Mikey 20 Feb '12

20 Feb '12

In 25 days I will get a netbook with windows ce 6 to view code, my pda won't edit or view code at least not fast so the new one will be better.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev