qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Friedt <chrisfriedt@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] mac development? cannot step with gdb
Date: Wed, 16 Mar 2016 14:45:10 -0400	[thread overview]
Message-ID: <CAF4BF-TVkykUp0Te=mLPCcPmuiXJD080Wu3+x83Cph=hJR2_iQ@mail.gmail.com> (raw)

Hi list,

I'm trying to implement some features in vmware_vga.c, so that I can
use a more recent vgabios-vmware.bin. My environment is Mac El Capitan
using clang and gdb. Perhaps using clang & gdb is my fatal flaw, but
I'm just not accustomed to using lldb yet.

Are there any others who primarily develop Qemu on a Mac? If so, what
debug environment are you using?

In any case, the specific issue I'm running into is this: Although
Qemu builds and runs well, and I can step through all parts of a
simple (or not simple)  'hello world' application, I am unable to step
through vmsvga_init() or any other function inside vmware_vga.c . I
can set a breakpoint and stop in those functions, but can't _step_
through any actual code. I wonder if that's the result of Mac + static
function + barf() or something..

<snip>
Thread 1 hit Breakpoint 1, 0x0000000100217d14 in vmsvga_init ()
(gdb) s
Single stepping until exit from function vmsvga_init,
which has no line number information.
0x0000000100217b52 in pci_vmsvga_realize ()
</snip>

Many devs on the list are undoubtedly familiar with the history of Mac
related debugging troubles..

Oh, the evil, fruity, walled-garden!!

I guess I may as well just try out lldb.

C

                 reply	other threads:[~2016-03-16 18:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAF4BF-TVkykUp0Te=mLPCcPmuiXJD080Wu3+x83Cph=hJR2_iQ@mail.gmail.com' \
    --to=chrisfriedt@gmail.com \
    --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).