On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
> which causes snprintf() to write beyond the end of the buffer.
>
> I've attached a patch that fixes it for me, but it's probably better not
> to create such large buffe
On 4/17/06, Jesse Allen <[EMAIL PROTECTED]> wrote:
> On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> > Jesse Allen wrote:
> > > On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> > >> Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
> > >> which causes snprintf(
Jesse Allen wrote:
> On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
>> Jesse Allen wrote:
>>> On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
which causes snprintf() to write beyond the end of the buffer
On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> Jesse Allen wrote:
> > On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> >> Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
> >> which causes snprintf() to write beyond the end of the buffer.
> >>
> >> I've attac
Jesse Allen wrote:
> On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
>> Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
>> which causes snprintf() to write beyond the end of the buffer.
>>
>> I've attached a patch that fixes it for me, but it's probably better not
>>
On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
> Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
> which causes snprintf() to write beyond the end of the buffer.
>
> I've attached a patch that fixes it for me, but it's probably better not
> to create such large buffe
Wine doesn't crash in this function, sorry, it's a bug in pf_vsnprintf()
which causes snprintf() to write beyond the end of the buffer.
I've attached a patch that fixes it for me, but it's probably better not
to create such large buffers on the stack.
Anyone with a better fix?
tom
diff --git a/dl
Hi,I think it trys to map the charector to the built-in ctable charector based on the locale.This function belongs to libwineunicode, ask Alexander for more info.Thanks and regards,Vijay
On 4/17/06, Tomas Carnecky <[EMAIL PROTECTED]> wrote:
These circumstances being if it tries to load an invalid l
These circumstances being if it tries to load an invalid lua file, more
specifically a lua file which contains the invalid lua string (not
character!) "\342\200\260".
I don't know what this function does and there isn't a TRACE() in that
function, so could someone please review if the function is
