From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU 0.5.2 testing
Date: Mon, 19 Jan 2004 11:49:09 +0100 [thread overview]
Message-ID: <400BB625.7020202@free.fr> (raw)
In-Reply-To: 20040119012751.GA9351@MAIL.13thfloor.at
Herbert Poetzl wrote:
> On Mon, Jan 19, 2004 at 12:09:11AM +0100, Fabrice Bellard wrote:
>
>>Hi,
>>
>>I commited all the current fixes in the CVS. I will make the 0.5.2
>>release tomorrow, so it would be interesting if some people could test
>>it before it is officially released...
>
>
> texi2html -monolithic -number qemu-doc.texi
> make: texi2html: Command not found
> make: *** [qemu-doc.html] Error 127
In the distribution I add the html et man files, so it should not be a
problem to most users (I am relunctant to add texi2html in the
distribution).
> usual set of compiler warnings, are you interested
> in that output too?
I know they are warnings in translate.c about a function prototype. If
you have others I am interested.
> seems to work as expected, with the folowing options
>
> qemu-cvs-19.01.2004/i386/qemu-fast -s -nographic -L qemu-0.5.1/pc-bios -m 128 -snapshot -hda IMGs/TEST_32M.img -hdb IMGs/TEST_256M.img -kernel <kernelpath>/arch/i386/boot/bzImage -append "rw root=/dev/hda1
>
> tested with/out -s for 2.4.24, 2.4.25-pre6 and 2.6.0 ...
> two harddisk images 32M and 256MB in size ...
So you don't use the '-kernel' option ? I am thinking about modifying
this option so that the PC bios is used in all cases (it would allow to
have the VGA output even with '-kernel'). A possible way would be to
integrate a custom linux loader ROM, as it is done now in plex86.
> hmm didn't notice that one until now (seems like a bug) ...
>
> Program received signal 0, Signal 0.
> default_idle () at process.c:92
> 92 }
> (gdb) break vfs_readdir
> Breakpoint 1 at 0x90152640: file readdir.c, line 17.
> (gdb) c
> Continuing.
>
> # ls /proc
> # ls /tmp
> # <nothing happens> CTRL-C
>
> Program received signal 0, Signal 0.
> default_idle () at process.c:92
> 92 }
> (gdb) break sys_vserver
> Breakpoint 2 at 0x901261f0: file vswitch.c, line 39.
> (gdb) c
> Continuing.
>
> # ls /tmp
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> vfs_readdir (file=0xc183c189, filler=0x2e9c103, buf=0xde89a5f3) at readdir.c:17
> 17 {
>
> (gdb) disable 1
> (gdb) c
> Continuing.
>
> # sys_vserver (call)
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> sys_vserver (cmd=0, id=0, data=0x0) at vswitch.c:39
> 39 {
Do you have the problem if you don't use gdb ? Maybe my last TLB
optimisations broke the gdb stub logic. I will check...
Fabrice.
next prev parent reply other threads:[~2004-01-19 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 23:09 [Qemu-devel] QEMU 0.5.2 testing Fabrice Bellard
2004-01-19 1:27 ` Herbert Poetzl
2004-01-19 10:49 ` Fabrice Bellard [this message]
2004-01-20 7:07 ` Herbert Poetzl
2004-01-21 16:15 ` Gabriel Ebner
2004-01-19 16:21 ` Jens Axboe
2004-01-20 0:14 ` J. Mayer
2004-01-20 4:07 ` Lennert Buytenhek
2004-01-20 10:45 ` J. Mayer
2004-01-21 11:43 ` Lennert Buytenhek
2004-01-21 21:53 ` J. Mayer
2004-01-26 9:19 ` Sylvain OBEGI
2004-01-26 11:48 ` Renzo Davoli
2004-01-20 17:09 ` Renzo Davoli
2004-01-20 17:26 ` Jens Axboe
2004-01-20 18:02 ` Renzo Davoli
2004-01-20 22:33 ` Chris Emerson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=400BB625.7020202@free.fr \
--to=fabrice.bellard@free.fr \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).