Am Friday 29 January 2010 01:20:24 schrieb Henri Verbeet:
> On 29 January 2010 00:21, Michael Stefaniuc wrote:
> > On 01/28/2010 10:59 PM, Henri Verbeet wrote:
> >> On 28 January 2010 22:39, Stefan Leichter
> >>
> >> wrote:
> >>> Is this a know problem? Is a work around available?
> >>
> >> Yeah,
Michael Stefaniuc writes:
> Anyway the usage of write(2) in NTDLL_dbg_vprintf() is *wrong* as it
> doesn't check for short writes nor errors. It is good enough for debug
> output and better than using the FILE * functions but not good enough to
> prevent interleaving. It even introduces an opport
Alexandre Julliard wrote:
> Michael Stefaniuc writes:
>
>> Incorrect. Wine doesn't use write(2) but vfprintf(3) which operates on
>> FILE handles; the output is buffered aka a vfprintf call won't translate
>> 1:1 to a write(2) system call. But even if it would directly use
>> write(2), that syste
Michael Stefaniuc writes:
> Incorrect. Wine doesn't use write(2) but vfprintf(3) which operates on
> FILE handles; the output is buffered aka a vfprintf call won't translate
> 1:1 to a write(2) system call. But even if it would directly use
> write(2), that system call isn't atomic. A lot of peop
Ken Thomases wrote:
> On Jan 28, 2010, at 5:21 PM, Michael Stefaniuc wrote:
>
>> On 01/28/2010 10:59 PM, Henri Verbeet wrote:
>>> On 28 January 2010 22:39, Stefan Leichter
>>> wrote:
Is this a know problem? Is a work around available?
>>> Yeah, that's a known problem. As a workaround y
On Jan 28, 2010, at 5:21 PM, Michael Stefaniuc wrote:
> On 01/28/2010 10:59 PM, Henri Verbeet wrote:
>> On 28 January 2010 22:39, Stefan Leichter
>> wrote:
>>> Is this a know problem? Is a work around available?
>>>
>> Yeah, that's a known problem. As a workaround you can use ">>"
>> (append) i
On 29 January 2010 00:21, Michael Stefaniuc wrote:
> On 01/28/2010 10:59 PM, Henri Verbeet wrote:
>>
>> On 28 January 2010 22:39, Stefan Leichter
>> wrote:
>>>
>>> Is this a know problem? Is a work around available?
>>>
>> Yeah, that's a known problem. As a workaround you can use ">>"
>> (append)
On 01/29/2010 12:23 AM, Nikolay Sivov wrote:
On 1/29/2010 02:21, Michael Stefaniuc wrote:
For the winefixme collector i have the luxury to be able to ignore the
mangled output lines; not so much for the wineoops crash collector.
Btw, are they ready and hosted somewhere already?
winefixme is "
On 1/29/2010 02:21, Michael Stefaniuc wrote:
For the winefixme collector i have the luxury to be able to ignore the
mangled output lines; not so much for the wineoops crash collector.
Btw, are they ready and hosted somewhere already?
bye
michael
On 01/28/2010 10:59 PM, Henri Verbeet wrote:
On 28 January 2010 22:39, Stefan Leichter wrote:
Is this a know problem? Is a work around available?
Yeah, that's a known problem. As a workaround you can use ">>"
(append) instead of ">" to redirect to the file. You'll still need the
"2>&1" to red
On 29 January 2010 00:14, Ben Klein wrote:
> 2010/1/29 Henri Verbeet :
>> On 28 January 2010 22:39, Stefan Leichter
>> wrote:
>>> Is this a know problem? Is a work around available?
>>>
>> Yeah, that's a known problem. As a workaround you can use ">>"
>> (append) instead of ">" to redirect to th
2010/1/29 Henri Verbeet :
> On 28 January 2010 22:39, Stefan Leichter wrote:
>> Is this a know problem? Is a work around available?
>>
> Yeah, that's a known problem. As a workaround you can use ">>"
> (append) instead of ">" to redirect to the file. You'll still need the
> "2>&1" to redirect stde
On 28 January 2010 22:39, Stefan Leichter wrote:
> Is this a know problem? Is a work around available?
>
Yeah, that's a known problem. As a workaround you can use ">>"
(append) instead of ">" to redirect to the file. You'll still need the
"2>&1" to redirect stderr to stdout, of course.
Hello,
does anyone notice a problem that the lines of the logging are written over
each other as in the attached log?
My system has an AMD Phenom(tm) II X2 550 Processor on a NVIDIA GeForce 8300
Chipset running running Debian Lenny 32 bit
Is this a know problem? Is a work around available?
--
14 matches
Mail list logo
