Hello Everyone!
After I saw an article mentioning you're using WinDbg for debugging, I
thought that information below could be interesting for you:
We (radare2 project) have developed our own implementation of both GDB
and WinDbg protocol parsers as a separate libraries in pure C and
without hard dependencies of external libraries.
Here you can find our WinDbg protocol implementation
https://github.com/radare/radare2/tree/master/shlr/wind
And here you can find our PDB parser
https://github.com/radare/radare2/tree/master/libr/bin/pdb
This is how to use radare2 for connecting to WinDbg server
https://github.com/radare/radare2/blob/master/doc/windbg
And here is how to use radare2 for parsing PDB files
https://github.com/radare/radare2/blob/master/doc/pdb/pdb_usage
Our goal is to write complete implementations of WinDbg and PDB, both
platform independent and working everywhere.
If you're interested on joining forces for that - feel free to answer
this email or join us in Telegram or IRC - "#radare" on both.
I hope this would be useful for someone.
Kind regards,
Anton Kochkov.
Hello guys,
My name is Federico Montanari and I am a student. I am from Italy and I
hope to join to ReactOS Team as web developer.
My skills:
- English and Italian Languages
- HTML and CSS (I'm learning Drupal)
- Base of C (Not WIN32 API)
Timezone: UTC +1
ReactOS Account name: decodp
ReactOS IRC name: decodp
What Can I do here?
I can write some articles about ReactOS Status or something, fix online
bugs and I can be moderator of forum and wiki to delete spam.
This is my proposal. Have you got any idea?
I ready to work on team (especially ReactOS Team)
You are a great team! Thank you for your work on ReactOS (I wrote one
program in C and.. it was difficult :p)
With my greetings,
Federico Montanari
Hello ReactOS community!
My name is Vardan.
First of all I want to say thank you to all the members of this community
who helped me to figure out status of works and make a proposal for GSoC.
Also I want to express my gratitude to those who makes decision to accept
my proposal. It is very responsible for me to be accepted for this project.
You can be sure that I'll do my best to be able to meet your expectations.
For all other members of ReactOS community, I want to introduce myself. I
am 1st year master student from Armenia. I have about 2 years of Linux
Driver development experience. My GSoC project title is "Improve ReactOS
USB stack" and I will be very grateful for any help from anyone of you. I
can easily communicate on Russian and English.
During this month after submission and before acceptance I have done some
investigation of ReactOS and it's built environment. Related to RosBE I
want to express separate thanks to them who created such environment where
newbies like me are able to easily build and test ReactOS and it's drivers
(even with MSVS!). ReactOS wiki page is also very helpful!
I have started Investigation of NT driver concepts with "Microsoft Windows
Internals" book and some online articles. Any recommendations related
sources of information are strongly appreciated by me.
I hope that this GSoC project will be a good starting point for me, to join
to "very small and exclusive ranks of people who know how to do NT systems
development" :)
Best regards,
Vardan.
Thomas, the standard says:
"If one of the strings has an encoding prefix and the other doesn't,
the one that doesn't will be considered to have the same encoding
prefix as the other."
In other words, this now sends a wide-string to ASSERTMSG. Which is wrong.
Best regards,
Alex Ionescu
On Sun, Apr 24, 2016 at 5:14 AM, Thomas Faber <thomas.faber(a)reactos.org> wrote:
> On 2016-04-20 14:16, akhaldi(a)svn.reactos.org wrote:
>> [CLASSPNP] Fix MSVC build. Brought to you by Timo.
>
>> --- trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] (original)
>> +++ trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] Wed Apr 20 12:16:16 2016
>> @@ -877,7 +877,7 @@
>> status = devInfo->ClassStopDevice(DeviceObject, IRP_MN_STOP_DEVICE);
>>
>> ASSERTMSG("ClassDispatchPnp !! STOP_DEVICE should "
>> - "never be failed\n", NT_SUCCESS(status));
>> + L"never be failed\n", NT_SUCCESS(status));
>>
>> if(isFdo) {
>> status = ClassForwardIrpSynchronous(commonExtension, Irp);
>>
>
> This makes no sense to me at all. You're now concatenating a narrow and
> a wide string (which should be an error, but compilers suck), and
> passing it to a macro that calls RtlAssert -- which expects a narrow
> string.
> Am I missing something here?
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
Given there seems to be no place where s is checked for length, it would
be more appropriated to perform such as check:
if ((!joliet && strlen(s) > MAX_EXTENSION_LENGTH) || strlen(s) >
MAX_NAME_LENGTH)
Le 24/04/2016 20:59, spetreolle(a)svn.reactos.org a écrit :
> Author: spetreolle
> Date: Sun Apr 24 18:59:33 2016
> New Revision: 71201
>
> URL: http://svn.reactos.org/svn/reactos?rev=71201&view=rev
> Log:
> [CDMAKE]
> Don't check for extension length on Joliet images.
> Encountered with AHK binaries.
>
> ONLINE-567
>
> Modified:
> trunk/reactos/sdk/tools/cdmake/cdmake.c
>
> Modified: trunk/reactos/sdk/tools/cdmake/cdmake.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/sdk/tools/cdmake/cdmake.c?…
> ==============================================================================
> --- trunk/reactos/sdk/tools/cdmake/cdmake.c [iso-8859-1] (original)
> +++ trunk/reactos/sdk/tools/cdmake/cdmake.c [iso-8859-1] Sun Apr 24 18:59:33 2016
> @@ -692,7 +692,8 @@
> error_exit("'%s' is not ISO-9660, aborting...", filename);
> s++;
> }
> - if (strlen(s) > MAX_EXTENSION_LENGTH)
> + // Check for extension length
> + if (!joliet && strlen(s) > MAX_EXTENSION_LENGTH)
> {
> error_exit("'%s' has too long extension, aborting...", filename);
> }
>
>
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
On 2016-04-20 14:16, akhaldi(a)svn.reactos.org wrote:
> [CLASSPNP] Fix MSVC build. Brought to you by Timo.
> --- trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/storage/classpnp/class.c [iso-8859-1] Wed Apr 20 12:16:16 2016
> @@ -877,7 +877,7 @@
> status = devInfo->ClassStopDevice(DeviceObject, IRP_MN_STOP_DEVICE);
>
> ASSERTMSG("ClassDispatchPnp !! STOP_DEVICE should "
> - "never be failed\n", NT_SUCCESS(status));
> + L"never be failed\n", NT_SUCCESS(status));
>
> if(isFdo) {
> status = ClassForwardIrpSynchronous(commonExtension, Irp);
>
This makes no sense to me at all. You're now concatenating a narrow and
a wide string (which should be an error, but compilers suck), and
passing it to a macro that calls RtlAssert -- which expects a narrow
string.
Am I missing something here?
Are you equally confused when Windows 10 Anniversary Update preview
builds also present themselves as such, even though it'snot coming out
until later?
Best regards,
Alex Ionescu
On Wed, Apr 13, 2016 at 9:31 AM, Javier Agustìn Fernàndez Arroyo
<elhoir(a)gmail.com> wrote:
> what about changing "-" by "+"?
>
> "0.4+SVNx"
> that would mean, "this is the 0.4. version, plus svn revisions until x"
>
>
> On Sun, Apr 10, 2016 at 11:25 PM, Mark Jansen <learn0more+ros(a)gmail.com>
> wrote:
>>
>>
>>
>> This way of numbering seems very confusing to me, and I assume to other
>> people as well..
>> When ReactOS presents itself as 0.5-SVN, I would expect this to be a 0.5
>> release, and not a 0.4 release that is working towards a 0.5.
>>
>>
>> regards,
>>
>> Mark
>>
>>
>> PS: I wasn't subscribed at the time this was sent, so sending a 'fake'
>> reply :)
>>
>>
>>> Ged Murphy gedmurphy.maillists at gmail.com
>>> Mon Feb 29 16:07:49 UTC 2016
>>>
>>> Because that’s what is being worked towards now, and there will be an
>>> unknown number of point releases until it’s reached.
>>>
>>> It’s also a bit of nostalgia, it’s what we’ve always done :)
>>>
>>>
>>>
>>>> From: Ros-dev [mailto:ros-dev-bounces at reactos.org] On Behalf Of
>>>> Hermès
>>>> BÉLUSCA - MAÏTO
>>>> Sent: 29 February 2016 16:00
>>>> To: ReactOS Development List <ros-dev at reactos.org>
>>>> Subject: [ros-dev] ReactOS SVN version naming
>>>>
>>>> Hi guys,
>>>>
>>>> I would like to understand what’s the rationale behind changing the
>>>> ReactOS
>>>> trunk version from “0.4-SVN” to “0.5-SVN” (see revision 70818) whereas
>>>> we
>>>> have just started to release ROS 0.4.0 only?
>>>>
>>>> Thanks in advance for your explanations!
>>>>
>>>> Cheers,
>>>> Hermès.
>>
>>
>> _______________________________________________
>> 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
>
This way of numbering seems very confusing to me, and I assume to other
people as well..
When ReactOS presents itself as 0.5-SVN, I would expect this to be a 0.5
release, and not a 0.4 release that is working towards a 0.5.
regards,
Mark
PS: I wasn't subscribed at the time this was sent, so sending a 'fake'
reply :)
*Ged Murphy* gedmurphy.maillists at gmail.com
> <ros-dev%40reactos.org?Subject=Re%3A%20%5Bros-dev%5D%20ReactOS%20SVN%20version%20naming&In-Reply-To=%3C005201d1730b%2456b98b90%24042ca2b0%24%40gmail.com%3E>
> *Mon Feb 29 16:07:49 UTC 2016*
>
> Because that’s what is being worked towards now, and there will be an
> unknown number of point releases until it’s reached.
>
> It’s also a bit of nostalgia, it’s what we’ve always done :)
>
>
>
>>
>> From: Ros-dev [mailto:ros-dev-bounces at reactos.org <http://www.reactos.org/mailman/listinfo/ros-dev>] On Behalf Of Hermès
>> BÉLUSCA - MAÏTO
>> Sent: 29 February 2016 16:00
>> To: ReactOS Development List <ros-dev at reactos.org <http://www.reactos.org/mailman/listinfo/ros-dev>>
>> Subject: [ros-dev] ReactOS SVN version naming
>>
>> Hi guys,
>>
>> I would like to understand what’s the rationale behind changing the ReactOS
>> trunk version from “0.4-SVN” to “0.5-SVN” (see revision 70818) whereas we
>> have just started to release ROS 0.4.0 only?
>>
>> Thanks in advance for your explanations!
>>
>> Cheers,
>> Hermès.
>
>
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of a month, 31th of March, 19:00 UTC, as usual. That's tomorrow!
IRC service will only be started shortly before the meeting. Your
participation passwords and server address 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.
Please send agenda proposals to me before the meeting. And yes, 0.4.1
release discussion is in the agenda list already, proposed by Alex Rex :-)
Regards,
Aleksey Bragin
Hi all,
After the plugs at our old hosting site have finally been pulled
yesterday, I managed to save all the important data and bring up a new
server. The following services are up again, even if their performance
might not match the old one:
* Build GCCLin_x86
* Build GCCLin_x86 Release
* Test KVM
* iso.reactos.org
In a short timeframe, I may be able to revive the Windows 7 builder as
well as Doxygen and download.reactos.org. Needs some evaluation as to
whether the resources of the server manage that.
Approximately around May or June, we can add some of our previous
servers to the server farm again. All services should be back up by
then, with the same or even improved performance.
Cheers,
Colin
Hello,
unfortunately I can't attend this meeting because of another official
appointment. Nevertheless I would like to offer support the GSoC student as
contact or mentor of necessary. Rama already contacted me and I reviewed his
proposal last week. As long as it is on the optional list of projects I deem
necessary to mention this.
Regards,
Matthias
Am Wednesday 30 March 2016 20:15:08 schrieb Aleksey Bragin:
> Hello,
> Let me invite you to the monthly status meeting taking place last
> Thursday of a month, 31th of March, 19:00 UTC, as usual. That's tomorrow!
>
> IRC service will only be started shortly before the meeting. Your
> participation passwords and server address 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.
>
> Please send agenda proposals to me before the meeting. And yes, 0.4.1
> release discussion is in the agenda list already, proposed by Alex Rex :-)
>
> Regards,
> Aleksey Bragin
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
--
Matthias Kupfer phone +49 371 236 46 52
Wilhelm-Firl-Straße 21 mobile +49 160 859 43 54
09122 Chemnitz, Germany
Hello,
I am interested in participating at GSOC 2016 and ReactOS has attracted my
attention as being an interested project to work on. The project that aims
to fully integrate lwIP is the one that caught my attention so I sent an
application to it. I would be grateful if someone can provide some feedback
to my application.
Also, I tried to compile the ReactOS sources on my laptop, but I am having
some problems. I tried solving them with the help of someone on the IRC
channel, but that was unsuccessful. I have cloned the SVN repository in a
directory on my hard disk and installed the RoSBuildEnvironment for
Windows. When I run the "configure.cmd" script from the RoSBE terminal as
is explained in the tutorial I am getting the message "find: cmake version:
No such file or directory" which is strange because if I run the command
"cmake --version" in the same terminal I get "cmake version 3.2.1-ReactOS"
which means it is detecting cmake so there isn't a problem in my PATH
environment variable. Anyone can help me with some tips regarding this
issue?
Best regards,
Valentin Mitrea.
Hello, everyone. I have an issue with retrieving debugging info.
I've tried both: my built (debug, x32) version and yours one. I used 2
methods: putty serial
<https://reactos.org/wiki/VirtualBox#Getting_debug_output>, and VMware
Gateway <https://reactos.org/wiki/VirtualBox#Using_VMwareGateway>. All of
them have the same response.
OS: Windows 10 x64. Running ReactOS under Virtual Box. Debug log is
attached.
What is wrong? Or could you advise me more suitable place for asking such
kind of questions?
Hi!
My name is Alexey Elnatanov and I'm 2nd course student of Lomonosov Moscow
State University Faculty of Computational Mathematics and Cybernetics.
*Languages:* *Russian, English*
*Timesone:* *UTC +03:00*
*IRC Nickname:** InvalidPointer*
I have some skill in C, NASM, UNIX-based systems (basic architecture, RAM
organization, file systems, syscalls, IPC, etc.). Also like Python. In
React-OS I'm interested in *Applications Manager Rapps *because it's
description looks interesting for me and it's very helpful for React-OS
user, which is very inspiring.
And as for my most serious project, I was working at, it's Conway's Game of
Life parrallel realization, using multiple processes and UNIX IPC.
Glad to hear from somebody soon.
With best regards,
Alexey Elnatanov.
Hello
My name is Vlad Kudoyar and I'm a 3rd course student in
Donetsk National Technical Univercity (Ukraine). My
speciality is Computer Engineering.
Languages: Russian, English (I can easily read texts but
write with Google Translate :) ).
Timezone: UTC +03:00.
IRC Nickname: Vlad8161.
I will be able to spend almost all of my summer working
on this project. I have bodybuilding trainings 3 times a
week, but they don't take too much time.
In ROS project I want to work on NTFS driver. I think I
can cope with implementing RW features.
General milestones:
1. Implementing features to modify MFT records' attributes
2. Implementing create/delete MFT records functionality
3. Implementing journaling
I realize that this plan is easy to write but hard to
implement but it is another goot reason to try hard.
I had filesystem course in my university so I can imagine
what I have to work with. I know basic NTFS concepts
and structure of this file system, but I have too little
experience with driver development. I hope mentors will
help me in this field.
On 2016-03-20 20:30, pschweitzer(a)svn.reactos.org wrote:
> Seriously... GCC, you allow this?!
Apparently this is valid in newer C++ standards, so GCC allows it also
for C. It will warn with -pedantic, which is probably too... pedantic
for our code base unfortunately ;)