Daniel Hejduk writes:
Is there any way to build the kernel on Linux preferably Arch
Linux?
In a VM, sure. Otherwise, no. Here's a comment from a thread about
this topic, from a couple of years ago:
https://www.reddit.com/r/openbsd/comments/r6wj3c/comment/hmwhk4a/
Alexis.
On Sat, 11 May 2024 21:49:42 +0100,
Daniel Hejduk wrote:
>
> Is there any way to build the kernel on Linux preferably Arch Linux?
>
It is theoretically possible, but you need to change Makefiles a lot, and
probably to hack your toolchain.
--
wbr, Kirill
Hello again,
Is there any way to build the kernel on Linux preferably Arch Linux?
Best regards,
Daniel Hejduk
11. května 2024 22:05:50 SELČ, "Kirill A. Korinsky" napsal:
>On Sat, 11 May 2024 20:28:08 +0100,
>Daniel Hejduk wrote:
>>
>> I want to enable kern
> On 11 May 2024, at 22:28, Daniel Hejduk wrote:
>
> Hello,
> I want to enable kernel debugging how can I do it?
>
See ddb(4) man page.
> Best regards,
> Daniel Hejduk
On Sat, 11 May 2024 20:28:08 +0100,
Daniel Hejduk wrote:
>
> I want to enable kernel debugging how can I do it?
>
See: https://man.openbsd.org/options
--
wbr, Kirill
Hello,
I want to enable kernel debugging how can I do it?
Best regards,
Daniel Hejduk
On 2021-05-19, Brennan Vincent wrote:
> Hello,
>
> I have an x86_64 PC with no serial port - is it possible to run ddb
> remotely via a PCI-express or USB serial port adapter? Or does it only
> work on an actual motherboard serial port connection?
It is sometimes possible via PCIE but you will
Hello,
I have an x86_64 PC with no serial port - is it possible to run ddb
remotely via a PCI-express or USB serial port adapter? Or does it only
work on an actual motherboard serial port connection?
If not, how do most kernel developers do their development work? In VMs,
or on older hardwar
Hi All/
My laptop brings to kernel debugging after closing-openning lid.
orlov-nb$ uname -a
OpenBSD orlov-nb.lan 6.9 GENERIC.MP#453 amd64
bios0: vendor Dell Inc. version "A16" date 05/24/2018
bios0: Dell Inc. Inspiron 3721
orlov-nb$ sysctl |grep machdep
machdep.console_de
Hi,
I was debugging the OpenBSD kernel using Qemu and gdb.
Well, it depends on the task. You can follow the below link if it suits to
you and sees if it works for you.
http://bijanebrahimi.github.io/blog/remote-debugging-the-running-openbsd-kernel.html
In my case, I was debugging pledge(2) and a
Hi,
I was wondering how you guys debug your kernel?
Are you doing some vmd(8) voodoo ?
Recompiling every time you think you've found the error gets quite
exhausting over time.
g,
Stephan
On Sun, 2018-05-13 at 22:22 +0300, IL Ka wrote:
> AFAIK kgdb (remote debug) is not supported:
> http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-debugging-tt
> 335833.html#a341551
>
> You can debug running kernel but functionality is limited.
Thanks. Looks like using QEmu
AFAIK kgdb (remote debug) is not supported:
http://openbsd-archive.7691.n7.nabble.com/on-line-kernel-
debugging-tt335833.html#a341551
You can debug running kernel but functionality is limited.
Hello,
I'd like to dive into the bridge driver and I am trying to setup a
kernel debugging environment.
I chose to use VMM to do that but I don't seem to find a way to connect
my local gdb to the VMM console. I guess I would need another serial
device for KGDB, but I have not found
Hi!
does OpenBSD supports on-line kernel debugging as FreeBSD does[1]?
The only tutorial I managed to find was a fairly old one[2] by QEMU
over GNU/Linux but it seems kgdb(7) is removed since 6.2 (apparently
for not even working before[3]).
Thank you!
[1]:
https://www.freebsd.org/doc/en/books
nuary 08, 2013 6:44 AM
To: Justin Mayes
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
On 17:04 Mon 07 Jan , Justin Mayes wrote:
> I got this. I had 2 com ports on this old target desktop and when I
> switched the serial cable to the right one, it worked. I have working
> DDB kernel
On 17:04 Mon 07 Jan , Justin Mayes wrote:
> I got this. I had 2 com ports on this old target desktop and when I switched
> the serial cable to the right one, it worked. I have working DDB kernel with
> structs as well as a working kgdb kernel with current.
>
> Justin
Good. Any chance to get
...@openbsd.org] On Behalf Of
Justin Mayes
Sent: Monday, January 07, 2013 2:35 PM
To: misc@openbsd.org
Subject: Re: Kernel Debugging
So now that I got ddb working good I went back and built kernel with KGDB
options per the 'man KGDB' page. I followed the other steps and I have a
null modem cable
r
Cc: misc@openbsd.org
Subject: Re: Kernel Debugging
Your right. I can view that struct also. The other structs I tried must have
been out of scope. Thanks for your help Philip.
J
-Original Message-
From: Philip Guenther [mailto:guent...@gmail.com]
Sent: Sunday, December 23, 2012 6:5
On Wed, Dec 26, 2012 at 5:32 PM, Luis Useche wrote:
> I just tried today and I couldn't build it either. But the following simple
> patch fixed it for me:
...
> However this might be wrong. Most likely there is a good reason why that
> ifdef is there.
Well, does the resulting kernel run? Can it
27;unknown structure' for anything other than mbuf. Anyone have any kernel
> > debugging strategies they'd like to share?
> >
> >
> >
> > Justin
> >
> > [demime 1.01d removed an attachment of type application/pkcs7-signature
> which had a name
: Kernel Debugging
On Sun, Dec 23, 2012 at 1:34 PM, Justin Mayes wrote:
> I was looking into kernel debug options and found that trying to build
> a kernel with kgdb option enabled fails.
If no one uses it, it won't keep working. Submitting a patch to fix the
build would be a fir
. I have moved on to plan B which was to build with option DDB_STRUCT
> and the build is a success but the 'show struct' command always returns
> 'unknown structure' for anything other than mbuf. Anyone have any kernel
> debugging strategies they'd like to shar
success but the 'show struct' command always returns
> 'unknown structure' for anything other than mbuf. Anyone have any kernel
> debugging strategies they'd like to share?
DDB_STRUCT works for me for other structures. For example, here's a
session looking at a firefox
TRUCT
and the build is a success but the 'show struct' command always returns
'unknown structure' for anything other than mbuf. Anyone have any kernel
debugging strategies they'd like to share?
Justin
[demime 1.01d removed an attachment of type application/pkcs7-
"Peter Kay - Syllopsium" <[EMAIL PROTECTED]> writes:
> Given that I'm in a minority of kgdb users, what's everyone else using
> in cases like this?
I use printfs, pstat -d and ddb. Never use breakpoints since I don't
trust them, they mess up timing too much.
//art
On Tue, Oct 7, 2008 at 11:36 AM, Peter Kay - Syllopsium
<[EMAIL PROTECTED]> wrote:
> if_bridge and if_pppoe are both kernel level files, and I want to set
> breakpoints to find out where it is/isn't working, so kgdb seemed like the
> best thing to use.
>
> Given that I'm in a minority of kgdb users
From: "Ted Unangst" <[EMAIL PROTECTED]>
To: "Peter Kay - Syllopsium" <[EMAIL PROTECTED]>
You might be the only one using kgdb. Between 4.3 and 4.4 the pccom
device was folded into com, which may not have gone perfectly.
OK. A further question, then.
What I'm trying to do is debug if_bridge a
On Tue, Oct 7, 2008 at 9:43 AM, Peter Kay - Syllopsium
<[EMAIL PROTECTED]> wrote:
> Kgdb kernel debugging appears to have been broken in 4.4-CURRENT for a week
> if not longer. The exact same config file works creating a debug kernel
> under 4.3. I've updated kernel, userland
Kgdb kernel debugging appears to have been broken in 4.4-CURRENT for a week
if not longer. The exact same config file works creating a debug kernel
under 4.3. I've updated kernel, userland etc. The same thing happens under
every virtualised environment I throw it at (vmware, qemu, virtu
I'm trying to set up a virtualised qemu OpenBSD kernel debug
environment, with a reasonable amount of success, but am running into
the following problem on bootup :
com1: at isa0 port 0x2f8/8 irq 3panic: com_isa_attach: mapping failed
The operating system has halted
Presumably because the kern
On Sun, 5 Feb 2006, Nick Holland wrote:
Charles Sprickman wrote:
Hello all,
I'm still not able to get OpenBSD 3.4->3.8 loaded on my old firewall box.
It either freezes or panics when probing (or creating?) "rd0", which I
assume is the ramdisk used in the install. It runs 3.3 fine.
So rath
Charles Sprickman wrote:
Hello all,
I'm still not able to get OpenBSD 3.4->3.8 loaded on my old firewall
box. It either freezes or panics when probing (or creating?) "rd0",
which I assume is the ramdisk used in the install. It runs 3.3 fine.
So rather than just asking some random questions,
On Fri, 3 Feb 2006, Rogier Krieger wrote:
On 2/3/06, Charles Sprickman <[EMAIL PROTECTED]> wrote:
It either freezes or panics when probing (or creating?) "rd0", which I
assume is the ramdisk used in the install. It runs 3.3 fine.
Perhaps you need to look at the FAQ if you're running i386:
up
On 2/3/06, Charles Sprickman <[EMAIL PROTECTED]> wrote:
> It either freezes or panics when probing (or creating?) "rd0", which I
> assume is the ramdisk used in the install. It runs 3.3 fine.
Perhaps you need to look at the FAQ if you're running i386:
upgrading/reinstalling OpenBSD/i386 using bsd
Hello all,
I'm still not able to get OpenBSD 3.4->3.8 loaded on my old firewall box.
It either freezes or panics when probing (or creating?) "rd0", which I
assume is the ramdisk used in the install. It runs 3.3 fine.
So rather than just asking some random questions, I'd like to know how to
36 matches
Mail list logo
