All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Jean-Pierre Cartal <jean-pierre@cartal.fr>,
	Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Make 4.3 and printvars
Date: Sat, 4 Jun 2022 10:19:33 +0200	[thread overview]
Message-ID: <20220604081933.GD427639@scaer> (raw)
In-Reply-To: <6478648f-ffb3-cda2-66ad-3758ead25319@mind.be>

All,

On 2022-06-03 16:05 +0200, Arnout Vandecappelle spake thusly:
>  Sending this in name of Jean-Pierre, who is not on the list.
> >A quick mail to let you know that I also faced the make 4.3 printvars issue you mentioned in Buildroot mailing list.
> >On my side increasing the stack size limit as follow:
> >ulimit -s 16000
> >solved this issue.
>  I tested it myself and indeed, it works!

Unfortunately, it does not:

    $ make defconfig
    $ make allyespackageconfig

    $ ulimit -s
    8192
    $ make show-vars >/dev/null
    Segmentation fault (core dumped)

    $ ulimit -s 16000
    $ ulimit -s
    16000
    $ make show-vars >/dev/null
    [...]
    Segmentation fault (core dumped)

I guess it works by chance on "small-enough" configurations, but this is
still not guaranteed that it works all the times.

I'd rather have no workaround, than one that is half-functional.

Yes, the above *is* extreme, and a completely degenerate case, yet it
means the issue it still present for "big-enough" configurations (I
haven't tried to find how many packages must be enabled before we reach
the tripping point, but that's not the point).

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-06-04  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e123582d-c613-f81a-ac0d-b23bc4d3e74a@cartal.fr>
2022-06-03 14:05 ` [Buildroot] Make 4.3 and printvars Arnout Vandecappelle
2022-06-03 14:25   ` Giulio Benetti
2022-06-03 14:29     ` Giulio Benetti
2022-06-03 14:43   ` Thomas Petazzoni via buildroot
2022-06-04  8:19   ` Yann E. MORIN [this message]
2022-06-04 18:50     ` Giulio Benetti

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=20220604081933.GD427639@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=jean-pierre@cartal.fr \
    /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.