Hi,
actually it looks more like the program was compiled with
"-fomit-frame-pointer". For that reason, you only get correct names (and
EIPs) for library calls.
Since QEmu uses as many physical registers as it can get, it is sensible
to omit the frame pointer, because it has no meaning anyway once
On Sunday 31 July 2005 13:47, Rudi Lippert wrote:
> Should a qemu backtrace be 411 lines long?
> Actually, when I start qemu 0.7.1 (kqemu enabled, but makes no difference),
> it doesn't do anything. I hit CTRL-C to get a backtrace of the situation.
> Qemu has never worked on this setup, and the pro
Should a qemu backtrace be 411 lines long?
Actually, when I start qemu 0.7.1 (kqemu enabled, but makes no difference),
it doesn't do anything. I hit CTRL-C to get a backtrace of the situation.
Qemu has never worked on this setup, and the problem has always been the
same.
Any ideas?
Cheers,
Rudi
