On 02/03/2010 08:30 PM, Roy Tam wrote:
2010/2/4 Roy Tam:
2010/2/3 Luiz Capitulino:
OK we are fooled by the json lexer and parser. As we use %I64d to
print 'long long' variables in Win32, but lexer and parser only deal
with %lld but not %I64d, this patch add support for %I64d and solve
On 02/04/2010 10:59 AM, Roy Tam wrote:
2010/2/4 Luiz Capitulino:
On Thu, 4 Feb 2010 10:30:30 +0800
Roy Tam wrote:
2010/2/4 Roy Tam:
2010/2/3 Luiz Capitulino:
OK we are fooled by the json lexer and parser. As we use %I64d to
print 'long long' variables in Win32, b
2010/2/4 Luiz Capitulino :
> On Thu, 4 Feb 2010 10:30:30 +0800
> Roy Tam wrote:
>
>> 2010/2/4 Roy Tam :
>> > 2010/2/3 Luiz Capitulino :
>>
>> OK we are fooled by the json lexer and parser. As we use %I64d to
>> print 'long long' variables in Win32, but lexer and parser only deal
>> with %lld but n
On Thu, 4 Feb 2010 10:30:30 +0800
Roy Tam wrote:
> 2010/2/4 Roy Tam :
> > 2010/2/3 Luiz Capitulino :
>
> OK we are fooled by the json lexer and parser. As we use %I64d to
> print 'long long' variables in Win32, but lexer and parser only deal
> with %lld but not %I64d, this patch add support for
2010/2/4 Roy Tam :
> 2010/2/4 Roy Tam :
>> 2010/2/3 Luiz Capitulino :
>
> OK we are fooled by the json lexer and parser. As we use %I64d to
> print 'long long' variables in Win32, but lexer and parser only deal
> with %lld but not %I64d, this patch add support for %I64d and solve
> 'info pci', 'pow
2010/2/4 Roy Tam :
> 2010/2/3 Luiz Capitulino :
OK we are fooled by the json lexer and parser. As we use %I64d to
print 'long long' variables in Win32, but lexer and parser only deal
with %lld but not %I64d, this patch add support for %I64d and solve
'info pci', 'powser_reset' and 'power_powerdown
2010/2/3 Luiz Capitulino :
> On Wed, 3 Feb 2010 10:09:07 +0800
> Roy Tam wrote:
>
>> 2010/2/2 Luiz Capitulino :
>> > On Tue, 2 Feb 2010 09:35:16 +0800
>> > Roy Tam wrote:
>> >
>> >> 2010/2/2 Luiz Capitulino :
>> >> > On Tue, 2 Feb 2010 00:26:53 +0800
>> >> > Roy Tam wrote:
>> >> >
>> >> >> 2010/
On Wed, 3 Feb 2010 10:09:07 +0800
Roy Tam wrote:
> 2010/2/2 Luiz Capitulino :
> > On Tue, 2 Feb 2010 09:35:16 +0800
> > Roy Tam wrote:
> >
> >> 2010/2/2 Luiz Capitulino :
> >> > On Tue, 2 Feb 2010 00:26:53 +0800
> >> > Roy Tam wrote:
> >> >
> >> >> 2010/2/2 Luiz Capitulino :
> >> >>
> >> >> >
2010/2/2 Luiz Capitulino :
> On Tue, 2 Feb 2010 09:35:16 +0800
> Roy Tam wrote:
>
>> 2010/2/2 Luiz Capitulino :
>> > On Tue, 2 Feb 2010 00:26:53 +0800
>> > Roy Tam wrote:
>> >
>> >> 2010/2/2 Luiz Capitulino :
>> >>
>> >> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
>> >
On Tue, 2 Feb 2010 09:35:16 +0800
Roy Tam wrote:
> 2010/2/2 Luiz Capitulino :
> > On Tue, 2 Feb 2010 00:26:53 +0800
> > Roy Tam wrote:
> >
> >> 2010/2/2 Luiz Capitulino :
> >>
> >> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> >> > is the last qemu's function I see in
2010/2/2 Luiz Capitulino :
> On Tue, 2 Feb 2010 00:26:53 +0800
> Roy Tam wrote:
>
>> 2010/2/2 Luiz Capitulino :
>>
>> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
>> > is the last qemu's function I see in the logs.
>> >
>> > From now on I only see msvcrt functions...
>>
On Tue, 2 Feb 2010 00:26:53 +0800
Roy Tam wrote:
> 2010/2/2 Luiz Capitulino :
>
> > Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> > is the last qemu's function I see in the logs.
> >
> > From now on I only see msvcrt functions...
> >
> > Maybe, you can type run on gdb
2010/2/2 Luiz Capitulino :
>
> Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> is the last qemu's function I see in the logs.
>
> From now on I only see msvcrt functions...
>
> Maybe, you can type run on gdb, run system_reset on the
> Monitor and then switch back to gdb an
2010/2/2 Luiz Capitulino :
> Hm, I'm puzzled. Is this failing on malloc()? At least qemu_malloc()
> is the last qemu's function I see in the logs.
>
> From now on I only see msvcrt functions...
>
> Maybe, you can type run on gdb, run system_reset on the
> Monitor and then switch back to gdb and
On Mon, 1 Feb 2010 21:42:37 +0800
Roy Tam wrote:
> 2010/2/1 Luiz Capitulino :
> > On Mon, 1 Feb 2010 20:36:22 +0800
> > Roy Tam wrote:
> >
> >> 2010/2/1 Luiz Capitulino :
> >> > On Sun, 31 Jan 2010 16:28:42 +0800
> >> > Roy Tam wrote:
> >> >
> >> >> Dear all,
> >> >>
> >> >> In latest git revis
2010/2/1 Luiz Capitulino :
> On Mon, 1 Feb 2010 20:36:22 +0800
> Roy Tam wrote:
>
>> 2010/2/1 Luiz Capitulino :
>> > On Sun, 31 Jan 2010 16:28:42 +0800
>> > Roy Tam wrote:
>> >
>> >> Dear all,
>> >>
>> >> In latest git revision, when guest OS restarts or system_reset command
>> >> issues from mon
On Mon, 1 Feb 2010 20:36:22 +0800
Roy Tam wrote:
> 2010/2/1 Luiz Capitulino :
> > On Sun, 31 Jan 2010 16:28:42 +0800
> > Roy Tam wrote:
> >
> >> Dear all,
> >>
> >> In latest git revision, when guest OS restarts or system_reset command
> >> issues from monitor console, it asserts failed:
> >> As
2010/2/1 Luiz Capitulino :
> On Sun, 31 Jan 2010 16:28:42 +0800
> Roy Tam wrote:
>
>> Dear all,
>>
>> In latest git revision, when guest OS restarts or system_reset command
>> issues from monitor console, it asserts failed:
>> Assertion failed: obj != NULL, file C:/msys/home/User/qemu/monitor.c, l
On Sun, 31 Jan 2010 16:28:42 +0800
Roy Tam wrote:
> Dear all,
>
> In latest git revision, when guest OS restarts or system_reset command
> issues from monitor console, it asserts failed:
> Assertion failed: obj != NULL, file C:/msys/home/User/qemu/monitor.c, line 338
Hm, I can't reproduce this
Dear all,
In latest git revision, when guest OS restarts or system_reset command
issues from monitor console, it asserts failed:
Assertion failed: obj != NULL, file C:/msys/home/User/qemu/monitor.c, line 338
Best regards,
Roy Tam
20 matches
Mail list logo