Dear all,
My name is Vyron Tsingaras a 23 year old currently employed as a Systems
and Network Administrator at AMD Telecom S.A.
My work duties involve maintainance and installation of Linux servers,
XenSerevr hypervisors, networking equipment (Cisco ISR, Cisco ITP, Cisco
ASA, Fortigate firewalls, Mikrotik routers, pfSense firewalls) and basic
MySQL administration. I love using Ops automation tools (pref. Ansible) and
have experience scripting and developing in Python.
I have followed ReactOS for quite some time and me being an unqualified
programmer for systems programming for contributing code to such a complex
project I feel that this is a position I am better qualified for.
I am from Greece (UTC+2) and my work hours are 9-5.30. I will be available
after work hours and on weekends always providing notifcation if I will be
unavailable.
I feel excited at the prospect of contributing to an open source project of
this scale and look forward to working with all of you should I be accepted.
Best Regards,
Vyron Tsingaras.
On 2016-08-20 11:43, gadamopoulos(a)svn.reactos.org wrote:
> --- trunk/reactos/dll/win32/shell32/shlfileop.cpp [iso-8859-1] (original)
> +++ trunk/reactos/dll/win32/shell32/shlfileop.cpp [iso-8859-1] Sat Aug 20 09:43:09 2016
> @@ -1480,6 +1480,19 @@
> return 0;
> }
>
> + /* Check files. Do not delete one if one file does not exists */
> + for (i = 0; i < flFrom->dwNumFiles; i++)
> + {
> + fileEntry = &flFrom->feFiles[i];
> +
> + if ((HANDLE)fileEntry->attributes == INVALID_HANDLE_VALUE)
What's wrong with INVALID_FILE_ATTRIBUTES?
> + {
> + // This is a windows 2003 server specific value which has been removed.
> + // Later versions of windows return ERROR_FILE_NOT_FOUND.
> + return ERROR_SHELL_INTERNAL_FILE_NOT_FOUND;
> + }
> + }
> +
> for (i = 0; i < flFrom->dwNumFiles; i++)
> {
> bPathExists = TRUE;
Hello,
Let me invite you to the monthly status meeting taking place this
Thursday, 25th of August, 19:00 UTC.
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.
The backup place to conduct meetings is #reactos-meeting channel on
Freenode.
Please send agenda proposals to me before the meeting so we don't waste
time trying to setup the agenda directly during the meeting.
Regards,
Aleksey Bragin
Sorry, I had forgotten this:
Le 23/08/2016 à 00:24, jgardou(a)svn.reactos.org a écrit :
> Author: jgardou
> Date: Mon Aug 22 22:24:30 2016
> New Revision: 72435
>
> URL: http://svn.reactos.org/svn/reactos?rev=72435&view=rev
> Log:
> [KDGDB]
> - Implement setting and removing breakpoints
> - Implement single-stepping
> - Only get past the breakpoint instruction when it comes from RtlpBreakWithStatus
> - Implement writing to memory
> - Always send the thread raising the exception to GDB to avoid confusing it
> - Let GDB find the program counter alone by querying the registers (support was already there before.)
> - Properly escape special characters on input
> Ladies and gentlemen : the almost-fully functional GDB stub. (still no real multi-process support :-( )
> To enable , in CMakeCache.txt :
> - Set GDB:BOOL=TRUE
> - Set _WINKD_:BOOL=TRUE
> - Set KDBG:BOOL=FALSE
> To do : give GDB the list of loaded drivers. Loading ntoskrnl.exe symbols at 0x80801000 already does a good enough job.
> Default output is on COM1. Can be configure to any othe COM port with usual kernel options.
> Hope you'll like it as much as I do ;-)
>
> Modified:
> trunk/reactos/drivers/base/kdgdb/gdb_input.c
> trunk/reactos/drivers/base/kdgdb/gdb_receive.c
> trunk/reactos/drivers/base/kdgdb/gdb_send.c
> trunk/reactos/drivers/base/kdgdb/i386_sup.c
> trunk/reactos/drivers/base/kdgdb/kdcom.c
> trunk/reactos/drivers/base/kdgdb/kdgdb.h
> trunk/reactos/drivers/base/kdgdb/kdpacket.c
>
> Modified: trunk/reactos/drivers/base/kdgdb/gdb_input.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/drivers/base/kdgdb/gdb_inp…
> ==============================================================================
> --- trunk/reactos/drivers/base/kdgdb/gdb_input.c [iso-8859-1] (original)
> +++ trunk/reactos/drivers/base/kdgdb/gdb_input.c [iso-8859-1] Mon Aug 22 22:24:30 2016
> @@ -9,6 +9,11 @@
>
> /* LOCALS *********************************************************************/
> static ULONG_PTR gdb_run_tid;
> +static struct
> +{
> + ULONG_PTR Address;
> + ULONG Handle;
> +} BreakPointHandles[32];
>
>
> /* GLOBALS ********************************************************************/
> @@ -203,16 +208,15 @@
>
> if (!Resuming)
> {
> + /* Report the idle thread */
> +#if MONOPROCESS
> + ptr += sprintf(ptr, "1");
> +#else
> + ptr += sprintf(gdb, "p1.1");
> +#endif
That looks highly suspicious?
Shouldn't it be ptr += sprintf(ptr, "p1.1");
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.