From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: building debug version of klibc
Date: Sat, 30 Dec 2017 07:38:17 -0500 [thread overview]
Message-ID: <242563.1514637497@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CADxRZqz54xbBVucSfipzjViAa7=j5WiLodM_5i0-88szjbxB5Q@mail.gmail.com>
On Sat, 30 Dec 2017 15:27:17 +0300, Anatoly Pugachev said:
> I'm using / testing a git kernel upstream on my hardware (sparc64 /
> ppc64 / ia64 ).
> Only this time, installing latest git kernel, I get a sigserv on
> sparc64 from klibc utility (fstype), and posted about it to mailing
> list.
> So, to properly report with gdb backtrace, i was need to build klibc
You didn't have to re-install the kernel, just get the klibc files installed.
At worst, you only have to rebuild an initramfs.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171230/4b32e6d4/attachment.bin
WARNING: multiple messages have this Message-ID (diff)
From: valdis.kletnieks@vt.edu
To: kernelnewbies@lists.kernelnewbies.org
Subject: Re: building debug version of klibc
Date: Sat, 30 Dec 2017 12:38:17 +0000 [thread overview]
Message-ID: <242563.1514637497@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CADxRZqz54xbBVucSfipzjViAa7=j5WiLodM_5i0-88szjbxB5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
On Sat, 30 Dec 2017 15:27:17 +0300, Anatoly Pugachev said:
> I'm using / testing a git kernel upstream on my hardware (sparc64 /
> ppc64 / ia64 ).
> Only this time, installing latest git kernel, I get a sigserv on
> sparc64 from klibc utility (fstype), and posted about it to mailing
> list.
> So, to properly report with gdb backtrace, i was need to build klibc
You didn't have to re-install the kernel, just get the klibc files installed.
At worst, you only have to rebuild an initramfs.
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next prev parent reply other threads:[~2017-12-30 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 10:54 building debug version of klibc Anatoly Pugachev
2017-12-30 11:30 ` Sam Ravnborg
2017-12-30 12:00 ` Anatoly Pugachev
2017-12-30 12:00 ` Anatoly Pugachev
2017-12-30 12:00 ` valdis.kletnieks at vt.edu
2017-12-30 12:05 ` Anatoly Pugachev
2017-12-30 12:05 ` Anatoly Pugachev
2017-12-30 12:14 ` valdis.kletnieks at vt.edu
2017-12-30 12:14 ` valdis.kletnieks
2017-12-30 12:27 ` Anatoly Pugachev
2017-12-30 12:27 ` Anatoly Pugachev
2017-12-30 12:38 ` valdis.kletnieks at vt.edu [this message]
2017-12-30 12:38 ` valdis.kletnieks
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=242563.1514637497@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.