Marius Groeger wrote:
I agree, though, that in your debugging, you probably examined a wrong
context. The actual, current context's EXL should be correct, otherwise
things wouldn't be working at all.
Argh, debugging different context sounds nice ;) It's my
feeling that while switching between
On Wed, 16 Aug 2006, Dirk Behme wrote:
AFAIU qemu maintains an environment stack, I guess popping the
environment restores the old flag contents.
Anybody with a short explanation of the basics of this? I think this would
really help debugging this issue.
I don't think it's really a stack (s
Alex wrote:
> MSYS/MinGW on Athlon 1.25 GHz with 500MB of RAM, Windows XP Pro
>
> $ uname -a
> MINGW32_NT-5.1 VIC 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown
>
> $ gcc --version
> gcc.exe (GCC) 3.2.3 (mingw special 20030504-1)
>
> ./configure --target-list=i386-softmmu --static
> make
>
> I co
MSYS/MinGW on Athlon 1.25 GHz with 500MB of RAM, Windows XP Pro
$ uname -a
MINGW32_NT-5.1 VIC 1.0.10(0.46/3/2) 2004-03-15 07:17 i686 unknown
$ gcc --version
gcc.exe (GCC) 3.2.3 (mingw special 20030504-1)
./configure --target-list=i386-softmmu --static
make
I compiled several previous versions o
Alex
Some inevitable question others will ask:
what is your machine's configuration and build environment ?
MSYS ?
GCC ?
What versions of these tools ?
How are you invoking make ?
etc.
Regards
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
Of Ale
vl.o(.text+0x57b0): In function `do_savevm':
c:/qemu/vl.c:4570: undefined reference to `gettimeofday'
--
Alex.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Thiemo Seufer wrote:
Dirk Behme wrote:
I'm not sure, but while playing with MIPS interrupts, it
seems to me that something with reset of interrupt flag
MIPS_HFLAG_EXL (0x04) at exception exit (eret) is wrong. It
seems to me that only one interrupt is executed because
after eret, MIPS_HFLAG_EX
Dirk Behme wrote:
> Hi,
>
> I'm not sure, but while playing with MIPS interrupts, it
> seems to me that something with reset of interrupt flag
> MIPS_HFLAG_EXL (0x04) at exception exit (eret) is wrong. It
> seems to me that only one interrupt is executed because
> after eret, MIPS_HFLAG_EXL st
Hi,
I'm not sure, but while playing with MIPS interrupts, it
seems to me that something with reset of interrupt flag
MIPS_HFLAG_EXL (0x04) at exception exit (eret) is wrong. It
seems to me that only one interrupt is executed because
after eret, MIPS_HFLAG_EXL stays set in env->hflags. Then,
Hi,
I am interesting to understand qemu network manage too. I search and find this document:
http://www.h7.dion.ne.jp/~qemu-win/HowToNetwork-en.html
Look if it can help you (I read it very fast but I think it's very interesting).
2006/8/14, S. P. T. Krishnan <[EMAIL PROTECTED]>:
Hi,I would like to
J M Cerqueira Esteves wrote:
> Host CPU: AMD Athlon 64 3500+ (machine: HP dx5150 MT)
> Host operating system: Ubuntu 6.06 LTS
> Host kernel: one of the Ubuntu pre-packaged ones,
> 2.6.15-26-amd64-k8 (SMP PREEMPT)
> QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa
> kqemu: 1
As I said before, under
Host CPU: AMD Athlon 64 3500+ (machine: HP dx5150 MT)
Host operating system: Ubuntu 6.06 LTS
Host kernel: one of the Ubuntu pre-packaged ones,
2.6.15-26-amd64-k8 (SMP PREEMPT)
QEMU: 0.8.2, configured with -cc=gcc-3.4 --enable-alsa
kqemu: 1.3.0pre9
I coul
12 matches
Mail list logo