public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivien Gallinaro <vivien.gallinaro@free.fr>
To: linux-kbuild@vger.kernel.org
Cc: Jesse T <mr.bossman075@gmail.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: SymSearch can cause make nconfig to segfault
Date: Fri, 10 Nov 2023 21:34:30 +0100	[thread overview]
Message-ID: <0cdc8c536da1e4bf5d7bae311c759f21@free.fr> (raw)
In-Reply-To: <1aab6cfd-1b87-42a8-9beb-02073bdf9add@infradead.org>


On 11/8/23, Randy Dunlap wrote:
> On 11/7/23, Jesse T wrote:
>> On 11/7/23 Vivien Gallinaro wrote:
>>> 
>>> For a fresh 6.6 kernel :
>>> $ cd linux-6.6
>>> $ make mrproper
>>> $ make nconfig 2>../blarb
>>> (<F8> x86 <enter>)
>>> $ reset
>> 
>> I'm assuming "reset" here means you got put back into your shell and 
>> are
>> resetting the terminal state.

Exactly.

>> I can not recreate this error on my machine unfortunately are you
>> using the tar release?
>> What distro are you using?

Gentoo, but checking with the (then) stable 6.6 tarball.

> I also cannot recreate this issue.
> FWIW.
> 
> More info needed.

That was good news. I tried to investigate a little deeper with strace, 
gdb… a little too deep for me actually. Then I eventually remembered: 
even though my install is pretty fresh, I've been a bit sloppy on 
maintenance, leaving one stuff to the side to catter to another, a few 
times over. One global update later — meaning I only have /usr/src in a 
corny state, now — I don't get the segfault either. Sorry, pebkac.

Thanks for your time,
VG


      reply	other threads:[~2023-11-10 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  2:30 SymSearch can cause make nconfig to segfault Vivien Gallinaro
2023-11-08  3:06 ` Jesse T
2023-11-08  6:00   ` Randy Dunlap
2023-11-10 20:34     ` Vivien Gallinaro [this message]

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=0cdc8c536da1e4bf5d7bae311c759f21@free.fr \
    --to=vivien.gallinaro@free.fr \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mr.bossman075@gmail.com \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox