similar to: [nbdkit] Windows errno handling

Displaying 20 results from an estimated 2000 matches similar to: "[nbdkit] Windows errno handling"

2020 Aug 17
0
Re: [nbdkit] Windows errno handling
On Mon, Aug 17, 2020 at 07:36:00PM +0100, Richard W.M. Jones wrote: > The Windows port of nbdkit > (https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw) now works > to some extent. However errno handling doesn't work. The way that > Winsock handles errors is incompatible with the way we expect to work > errno in several ways. The long story is here: > >
2020 Aug 17
2
Re: [nbdkit] Windows errno handling
On 8/17/20 1:46 PM, Daniel P. Berrangé wrote: > On Mon, Aug 17, 2020 at 07:36:00PM +0100, Richard W.M. Jones wrote: >> The Windows port of nbdkit >> (https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw) now works >> to some extent. However errno handling doesn't work. The way that >> Winsock handles errors is incompatible with the way we expect to work
2020 Aug 17
0
Re: [nbdkit] Windows errno handling
On Mon, Aug 17, 2020 at 01:56:10PM -0500, Eric Blake wrote: > On 8/17/20 1:46 PM, Daniel P. Berrangé wrote: > > On Mon, Aug 17, 2020 at 07:36:00PM +0100, Richard W.M. Jones wrote: > > > The Windows port of nbdkit > > > (https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw) now works > > > to some extent. However errno handling doesn't work. The way
2020 Aug 18
15
[PATCH nbdkit 0/9] Port to Windows.
Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many
2020 Aug 20
15
[PATCH nbdkit 0/13] Port to Windows without using a separate library.
Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in
2014 Aug 07
4
[PATCH 0/2] Fix errors found by Clang static analyzer
Hi, Here is one trivial initialization fix and another patch to convert a huge macro to an inline function. The result of the expansion would show up in an assertion which triggered a -Woverlength-strings warning. Peter Wu (2): Fix garbage return value on error Fix overly long assertion string lib/hivex-internal.h | 28 ++++++++++++++++------------ lib/node.c | 18
2013 Jul 25
19
[PATCH hivex 00/19] Fix read/write handling of li-records.
This is, hopefully, a full fix for handling of li-records. See: https://bugzilla.redhat.com/show_bug.cgi?id=717583 https://bugzilla.redhat.com/show_bug.cgi?id=987463 Rich.
2004 Aug 06
0
Submission: Patch to libshout/sock.c for MacOSX
Hi, re libshout: MacOSX doesn't have poll(), which prevents sock.c from compiling. I've patched sock.c to use select(), which is supported on MacOSX, and should be elsewhere too. I've marked my changes with "SKoT" comments in the file below. Main changes are in sock_write_bytes(). - SKoT ------8<----- /* sock.c * - General Socket Functions * * Copyright (c) 1999
2017 Feb 14
4
[PATCH v2 0/2] hivex: handle corrupted hives better
The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at
2017 Feb 16
6
[PATCH v4 0/5] hivex: handle corrupted hives better.
The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at
2017 Feb 15
2
[PATCH v3 0/2] hivex: handle corrupted hives better
The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be looking at
2017 Feb 08
4
[PATCH 0/2] hivex: handle corrupted hives better
Hello, The following patches address issues when dealing with hives that have corrupted data in them but are otherwise readable/writable. Those were found on some rather rare Windows installations that seem to work fine but current hivex fails to even open. Those patches change hivex to simply log and ignore such "corrupted" regions instead of aborting because the caller might be
2002 Feb 27
3
winsock 16 BIT
Hi! In October I worked with a client-server (using winsock.dll) 16 bit aplication emulated in wine (Not using ODBC), it worked fine. This aplication needs to connect to a server using port ctsql 5557/tcp, this service is in my /etc/services. And wine made all realy fine (Version 20011108). With the release 20011226 (I think)started the problem. Something changed with winsock 16-bit. I've
2009 Feb 09
2
Problem setting up a server on UDP port 59
I have a program that sets up a server on UDP port 59; it runs with no problem under windows XP. Under wine it fails, the log shows "Permission denied" for the WS_bind function. Has anyone else seen this? Does anyone know how to work around this? trace:winsock:WSAStartup succeeded trace:winsock:WS_socket af=2 type=1 protocol=0 trace:winsock:WSASocketA af=2 type=1 protocol=0
2011 May 10
3
Rift post 1.2 patch
game has failed for ALL wine users both under linux and Mac . we all get a a Rift error code as soon as we start the program.
2014 Feb 13
3
Libguestfs (1.22.6) driver/changes for mingw/win32
Hi, I attached the changes I made to a vanilla libguestfs-1.22.6 in order to make it work in mingw/win32. Added is also the patch required to make QEMU compatible (add a command to QMP that lists the supported devices (the regilat way you do it print it to stderr, which is difficult to redirect in win32)). This is done on behalf of Intel Corp. Thanks, Or (oberon in irc)
2017 Feb 15
2
Re: [PATCH v2 1/2] lib: change how hbin sections are read.
On Wed, Feb 15, 2017 at 01:48:29PM -0500, Dawid Zamirski wrote: > On Wed, 2017-02-15 at 16:54 +0000, Richard W.M. Jones wrote: > > On Tue, Feb 14, 2017 at 12:05:20PM -0500, Dawid Zamirski wrote: > > > * hivex_open: when looping over hbin sections (aka pages), handle a > > >   case where following hbin section may not begin at exactly at the > > > end > >
2009 Feb 15
3
EVE Online
Trying to run EVE Online through wine on my Asus EEEPC with a special flavor of Ubuntu called Easy Peasy built for netbooks. I run the app after doing all the necessary installation procedures and once the game goes full screen, I get sound just fine but the screen goes black and eventually freezes the computer entirely. I ran wine through terminal and got these errors: Code:
2008 Dec 02
3
CUPS Printers not showing up in wine (notepad et al)
I compiled and installed wine 1.1.8 (from src from winehq) probably 4 months ago...ish. I never tried printing until today after I installed MathCAD. My printer (which normally shows up in Ubuntu 8.04 32 bit) doesn't show up at all in wine. MathCAD and notepad both threw an error "Install a printer before trying to print" <- not exact quote. I tried installing bullzip pdf
2017 Feb 15
2
Re: [PATCH v2 1/2] lib: change how hbin sections are read.
On Wed, Feb 15, 2017 at 02:28:41PM -0500, Dawid Zamirski wrote: > Correct, however there's also no guarantee that seeking by 4k in > "garbage" data would not land you in registry data that happens to > evaluate to "hbin" as well. That's why I put "hbin" offset validation > check couple of lines below to make sure that the "hbin" we found