From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: ngn <ngn@ngn.tf>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Feedback on my development setup
Date: Thu, 18 Apr 2024 15:27:24 -0400 [thread overview]
Message-ID: <CAFkJGRdFuMoO4_mR-cR1NWjKQJnopN0v1R11-jSnLn+FKcOCdg@mail.gmail.com> (raw)
In-Reply-To: <CAFkJGRddGHK0j4CcQUoRKiD3afniLY=rRV5npY5wpauqqY0XZg@mail.gmail.com>
There's a type already. Term 1 should be:
qemu-system-x86_64 -s -cpu host -nographic -accel kvm -m 1G -kernel
arch/x86/boot/bzImage -append "root=/dev/sdb3 rw
console=ttyS0,115200n8" -drive
format=qcow2,file=$HOME/Downloads/Arch-Linux-x86_64-basic.qcow2
However, the kernel panics because it can't mount the root FS on an
unknown block. I don't know what the cause is. However, the UUIDs
are scrambled from what are in GRUB. Is there some sort of security
going on here?
On Thu, Apr 18, 2024 at 3:15 PM Josh Marshall
<joshua.r.marshall.1991@gmail.com> wrote:
>
> So the final outline would look like the following?
>
> Source:
> https://github.com/archlinux/arch-boxes
>
> setup:
>
> git clone $LINUX_REPO &
> wget https://geo.mirror.pkgbuild.com/images/latest/Arch-Linux-x86_64-basic.qcow2
>
> echo add-auto-load-safe-path
> “$LINUX_REPO_PATH/scripts/gdb/vmlinux-gdb.py” >>
> "$HOME/.config/gdb/gdbinit"
>
> echo ‘export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1’ >> $HOME/.bashrc
> echo ‘export USERCFLAGS=" -ggdb "’ >> $HOME/.bashrc
>
> push $LINUX_REPO_PATH
>
> echo “CONFIG_SATA_AHCI=y” >> .config
> echo “CONFIG_DEBUG_INFO=y” >> .config
> echo “CONFIG_DEBUG_INFO_DWARF5=y” >> .config
> echo “CONFIG_GDB_SCRIPTS=y” >> .config
> echo “CONFIG_GDB_INFO_REDUCED=n” >> .config
> echo “CONFIG_KGDB=y” >> .config
> echo “CONFIG_FRAME_POINTER=y” >> .config
> echo “CONFIG_KVM_GUEST=y” >> .config
> echo “CONFIG_RANDOMIZE_BASE=n” >> .config
>
> make localyesconfig
> pop
>
> source $HOME/.bashrc
> mkdir -p $HOME/mnt/arch
>
> Iterate:
> guestmount -w -a $HOME/Downloads/Arch-Linux-x86_64-basic.qcow2 -m
> /dev/sda3 ~/mnt/arch/
> <copy sources, files, perform compilation steps, etc as needed to
> inside the VM image as needed each development iteration>
> umount ~/mnt/arch
>
> Term 1:
> qemu-system-x86_64 -s -cpu host -nographic -accel kvm -m 1G -kernel
> vmlinux2 -append "root=/dev/sda3 rw console=ttyS0,115200n8 nokaslr
> " -drive format=qcow2,file=$HOME/Downloads/Arch-Linux-x86_64-basic.qcow2
>
> Term 2:
> gdb $LINUX_REPO_PATH/vmlinux
> : target remote:1234
> <set break points>
> : continue
>
> On Thu, Apr 18, 2024 at 11:36 AM ngn <ngn@ngn.tf> wrote:
> >
> > On Wed, Apr 17, 2024 at 05:18:34PM -0400, Josh Marshall wrote:
> > > One issue I'm seeing is that gdb isn't seeing debugging symbols. I'm
> > > getting the following output with the config linked.
> > >
> > > https://pastebin.com/tjq7QtQk
> > >
> > > ```
> > > anadon@botamon:~/Documents/code/linux$ gdb arch/x86/boot/bzImage
> > > GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
> > > Copyright (C) 2024 Free Software Foundation, Inc.
> > > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> > > This is free software: you are free to change and redistribute it.
> > > There is NO WARRANTY, to the extent permitted by law.
> > > Type "show copying" and "show warranty" for details.
> > > This GDB was configured as "x86_64-linux-gnu".
> > > Type "show configuration" for configuration details.
> > > For bug reporting instructions, please see:
> > > <https://www.gnu.org/software/gdb/bugs/>.
> > > Find the GDB manual and other documentation resources online at:
> > > <http://www.gnu.org/software/gdb/documentation/>.
> > >
> > > For help, type "help".
> > > Type "apropos word" to search for commands related to "word"...
> > > Reading symbols from arch/x86/boot/bzImage...
> > > (No debugging symbols found in arch/x86/boot/bzImage)
> > > ```
> > >
> >
> > You should load vmlinux to the gdb, not the bzImage. bzImage is a
> > compressed version of the kernel and its used boot, vmlinux is the
> > static ELF binary that contains the debugging symbols.
next prev parent reply other threads:[~2024-04-18 19:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:38 Feedback on my development setup Josh Marshall
2024-04-16 14:56 ` ngn
2024-04-16 15:03 ` Josh Marshall
2024-04-16 15:21 ` ngn
2024-04-17 16:11 ` Josh Marshall
[not found] ` <CAPzh0z8RySn429XYQHoP_c9UA+pb6SLHGhH40vQDhc3P2xiysQ@mail.gmail.com>
2024-04-17 21:18 ` Josh Marshall
2024-04-18 15:35 ` ngn
2024-04-18 19:15 ` Josh Marshall
2024-04-18 19:27 ` Josh Marshall [this message]
2024-04-18 19:52 ` Josh Marshall
2024-04-18 21:40 ` Josh Marshall
2024-04-19 16:14 ` ngn
2024-04-23 15:34 ` Josh Marshall
2024-04-23 16:08 ` Pranjal Singh
2024-04-23 16:39 ` Bilbao, Carlos
2024-04-23 17:43 ` Josh Marshall
2024-04-25 5:37 ` Josh Marshall
2024-04-25 14:36 ` Bilbao, Carlos
2024-04-25 14:54 ` Josh Marshall
2024-04-25 15:14 ` Jonathan Corbet
[not found] ` <CAFkJGReoq2s+LR1kj1hj8QvsKsEhk+CLYtCXV=DQTjTqan3DOg@mail.gmail.com>
2024-04-25 16:59 ` Carlos Bilbao
2024-04-25 17:08 ` Josh Marshall
2024-04-25 20:14 ` Theodore Ts'o
2024-04-25 20:02 ` Theodore Ts'o
2024-04-25 14:32 ` Thomas Bertschinger
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=CAFkJGRdFuMoO4_mR-cR1NWjKQJnopN0v1R11-jSnLn+FKcOCdg@mail.gmail.com \
--to=joshua.r.marshall.1991@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=ngn@ngn.tf \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).