‐‐‐ Original Message ‐‐‐
On Saturday, January 15th, 2022 at 17:03, Martin Husemann
wrote:
> On Sat, Jan 15, 2022 at 03:54:43PM +, pin wrote:
>
> > But, just so to clarify. The debug set is not pulled by sysinst and
> >
> > it used to be.
>
> I think it never was unless you manuall
On Sat, Jan 15, 2022 at 03:54:43PM +, pin wrote:
> But, just so to clarify. The debug set is not pulled by sysinst and
> it used to be.
I think it never was unless you manually select it in the sets menu.
The debug set does not strictly add functionality, so even a "full"
install does not use
Thank you both.
I've fetched the debug sets now and unpack them into place.
So, I can try to get a backtrace next time I get a coredump.
But, just so to clarify. The debug set is not pulled by sysinst and it used to
be.
> You did not update that recently, did you?
>
> This is with the latest download form nycdn:
>
> https://nycdn.NetBSD.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/sets/debug.tar.xz
>
> > tar tvzf debug.tar.xz | fgrep netbsd-
>
> -r--r--r-- 0 root bin 179990264 Jan 15 00:56
> ./usr/libdata/debug/
On Sat, Jan 15, 2022 at 03:22:24PM +, pin wrote:
> $ cd debug/
> $ ls -la
> total 32
> drwxr-xr-x 8 root wheel 512 Jan 8 18:25 .
> drwxr-xr-x 6 root wheel 512 Jan 8 18:25 ..
> drwxr-xr-x 2 root wheel 512 Jan 8 18:25 bin
> drwxr-xr-x 4 root wheel 512 Jan 8 18:25 lib
> drwxr-x
> The kernel debug symbols are installed in
> /usr/libdata/netbsd-.debug and
Now I'm feeling stupid. These is the default content of /usr/libdata directory,
$ ls -la
total 24
drwxr-xr-x 6 root wheel 512 Jan 8 18:25 .
drwxr-xr-x 16 root wheel 512 Jan 13 11:01 ..
drwxr-xr-x 8 root whe
> On Jan 15, 2022, at 9:43 AM, pin wrote:
>
>>> What should I run now instead?
>
>> If you have MKDEBUG set in your build or have installed the debug sets:
>
> Thanks!
> I don't think I follow, though. Sorry.
>
> I didn't build this kernel, the system was installed from a daily-build image.
On Sat, Jan 15, 2022 at 02:43:43PM +, pin wrote:
> > # gdb --eval-command="file /netbsd" --eval-command="target kvm
>
> Do you mean the debug symbols are baked into the kernel now?
No, they are in an external debug symbols file. The file name
is something like netbsd-GENERIC.debug and it shou
>> What should I run now instead?
> If you have MKDEBUG set in your build or have installed the debug sets:
Thanks!
I don't think I follow, though. Sorry.
I didn't build this kernel, the system was installed from a daily-build image.
> # gdb --eval-command="file /netbsd" --eval-command="target
In article
,
pin wrote:
>
>
>Sent with ProtonMail Secure Email.
>
>âââââââ Original Message âââââââ
>
>On Friday, January 14th, 2022 at 12:15 PM, Martin Husemann
> wrote:
>
>
>> The debug information moved, it is now stored in an external debug file
>>
>> in /usr/libd
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, January 14th, 2022 at 12:15 PM, Martin Husemann
wrote:
> The debug information moved, it is now stored in an external debug file
>
> in /usr/libdata/debug.
>
> Martin
Thank you!
But, where is netbsd.gdb located
On Fri, Jan 14, 2022 at 10:55:48AM +, pin wrote:
> Hi,
>
> As the title says, why is this the case?
> I had an install done from an image a day or two into January 2022 and it
> included /netbsd.gdb
The debug information moved, it is now stored in an external debug file
in /usr/libdata/debug
Hi,
As the title says, why is this the case?
I had an install done from an image a day or two into January 2022 and it
included /netbsd.gdb
Unfortunately, my system is still unstable and several crashes and core dumps
later, I got fs corruption.
So, I did a clean install.
$ uname -v
NetBSD 9.9
13 matches
Mail list logo
