qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] Enabling Debugging?


From: Jd Lyons
Subject: Re: [Qemu-ppc] Enabling Debugging?
Date: Tue, 31 Jan 2017 18:57:30 -0500


On Jan 31, 2017, at 1:57 PM, Thomas Huth <address@hidden> wrote:

On 31.01.2017 18:58, Jd Lyons wrote:
Finally got gdb to run, you don’t want to ask what you have to do on
MacOS Sierra to enable gdb, I’m think of giving up the Mac OS if this
continues.

Now when I launch qemu-system-ppc and type run, it opens, but hangs
before Openbios loads. So, I’m still doing something wrong.
[...]
Thread 2 received signal SIGUSR2, User defined signal 2.
0x00007fffa3e1f262 in ?? ()
(gdb)  

QEMU is using SIGUSR2 internally - but gdb always breaks at this signal
by default. Simply change the behavior of gdb to ignore this signal and
you should be fine. Something like:

handle SIGUSR2 noprint

(but it's been a while since I did that on my own, so the syntax might
be different...)

Thomas


Thanks Tom, that got it running, but I’m not getting anything useful from gdb.

I don’t want to debug with Qemu, I want to debug Qemu, itself. I tried searching for any documentation on how to do that with SIGUSR2, but I didn’t find much.

Should I be trying to use SIGUSR2?

Is there any documentation?

I’m trying to find out why Mac OS X Server 1.2v3, and all the other versions of OS X Server from 1.x, don’t have any input( KBD/Mouse ). I got Sever installed, if you give it the right OF tweeks and a pre-partitioned drive image, it will install, without any input from the user.

I can boot it, after it installs, from the HD image, but I can’t use it , b/c no keyboard and mouse. So, I’m trying to figure out how to debug that. It doesn’t hang, or crash, it just sits there, waiting for input.

It registers the ADB kbd/m on startup, in verbose mode, so I’m not sure where the trouble is. 

That’s with the g3beige target machine, with the mac99 target machine, it either hangs upon the start of [MPC} or it Kernel Panics. I’ll look into that later. tho I do have a question, for anyone that knows, why does Qemu put and ADB on mac99( G4 Agp Graphics )?

The Sawtooth didn’t have an ADB bus, that I remember, I think the G3 B&W and the G4 PCI Graphics had and ADB bus and some of the early  iMacs, I think those were the only NewWorld PPC Macs, that had an ADB bus. My problems my be unrelated to that tho, so if it works for others, I should just leave it alone.

I’m not really sure how I can debug with gdb, if the program is running, can’t find much documentation on how to do that. I did try with beer-process , but that didn’t seem to work.


 Can anyone offer any insight on how to debug this?

I tried passing -usb -device usb-hub,bus=usb-bus.0,port=1 -device usb-mouse,bus=usb-bus.0,port=1.2 -device usb-kbd,bus=usb-bus.0,port=1.1 to Qemu, and they did register in the Kernel, when Server boots in verbose mode, but they don’t work either.( g3beige boot will hang if USB kb/mouse are on different buses ).

 I also tried,  -usb -device usb-host,hostbus=4,hostaddr=1, altho that isn’t recommend by lsusb, it does work in Mac OS 9.2.1 and OS X 10.2/3. It hands the wireless receiver from my KB/M to the guest OS. Tho, when I give any input to OS X Sever, after the USB drivers load, the OS X Server freezes.

So, any one have any idea about how I can go about debugging this?

Any input, at all, I’m not picky ;-)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]