summaryrefslogtreecommitdiff
path: root/open_issues/debugging_gnumach_startup_qemu_gdb.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/debugging_gnumach_startup_qemu_gdb.mdwn')
-rw-r--r--open_issues/debugging_gnumach_startup_qemu_gdb.mdwn60
1 files changed, 59 insertions, 1 deletions
diff --git a/open_issues/debugging_gnumach_startup_qemu_gdb.mdwn b/open_issues/debugging_gnumach_startup_qemu_gdb.mdwn
index 3faa56fc..7b300ea1 100644
--- a/open_issues/debugging_gnumach_startup_qemu_gdb.mdwn
+++ b/open_issues/debugging_gnumach_startup_qemu_gdb.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2010, 2011, 2013 Free Software Foundation,
+[[!meta copyright="Copyright © 2010, 2011, 2013, 2014 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -144,3 +144,61 @@ See also discussion about *multiboot* on [[arm_port]].
<kilobug> matlea01: you need something with multiboot support (like grub)
to provide the various bootstrap modules to the kernel
<matlea01> Ah, I see
+
+
+## IRC, freenode, #hurd, 2014-02-24
+
+ <congzhang> hi, will grub load mach kernel to fix address? and which
+ address?
+ <congzhang> I want to use qemu gdb support to debug mach
+ <congzhang> need add-symble-file to right address
+ <youpi> congzhang: see objdump gnumach
+ <youpi> grub simply follows what's provided by the ELF format of the ELF
+ file
+ <nalaginrut> I think it's default value of _start in ELF, right?
+ <nalaginrut> hmm...the actual entry point should plus the size of
+ multi_boot header, at least 0xc...
+ <congzhang> youpi: I try that, but not works
+ <congzhang> I start qemu with -s
+ <congzhang> the /bin/console was very easy to cause black death, and I want
+ to use gdb to check whether the mach is death
+ <congzhang> I will try again later
+ <congzhang> Anyone know some tutorial to debug mach with qemu?
+ <nalaginrut> for better debug, I suggest bochs
+ <nalaginrut> although it's slower
+ <congzhang> nalaginrut: maybe it's my problem, I did not do the right thing
+ <congzhang> qemu with kvm was great.
+ <nalaginrut> qemu with kvm is cool to run, but not so cool for debug kernel
+ <nalaginrut> anyway, it's personal taste
+ <nalaginrut> you may use gdb for that
+ <nalaginrut> for bochs, you don't have to use external debugger
+ <congzhang> thanks for explain
+ <congzhang> does anyone succeed boot hurd with qemu multiboot boot
+ function?
+ <congzhang> with -kernel and -initrd command line parameter
+ <nalaginrut> I boot it with grub, in qemu, it's fine. Then I moved to
+ physical machine
+ <congzhang> boot with grub work for me too
+ <congzhang> I want to know whether it is possible to boot from qemu
+ directly
+ <congzhang> qemu can directly load kernel and hurd module for linux
+ <congzhang> nalaginrut: can you help to test whether hurd-console service
+ start will cause hurd black death?
+ <nalaginrut> I know qemu can boot Linux without MBR, but I don't know if
+ it's true for Hurd too
+ <nalaginrut> congzhang: I'm busy for other works now ;-)
+ <congzhang> ok, thks:)
+ <youpi> qemu's multiboot options don't seem to allow providing
+ ext2fs.static and ld.so, so I don't think it's possible
+ <congzhang> I try to do this, because hurd hurd-console cause system to
+ death very high frequency
+ <youpi> (because qemu doesn't implement all of multiboot)
+ <congzhang> qemu help show that's possible, -initrd support multi module
+ and parameter
+ <congzhang> en, I will check with them later
+ <youpi> how do you pass parameters to modules?
+ <youpi> ah, right, it's after the file name
+ <youpi> well, then simply try to pass the kernel, and the two modules
+ <youpi> with the same option as in the grub config templates
+ <youpi> it's fortunate that neither ext2fs nor exec need a comma on their
+ command line...