All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dmitry Chestnykh <dm.chestnykh@gmail.com>
Cc: yann.morin.1998@free.fr, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/busybox: Fallback to -g2 in if -g3 is enabled.
Date: Thu, 9 May 2024 16:33:45 +0200	[thread overview]
Message-ID: <20240509163345.4b91eca5@windsurf> (raw)
In-Reply-To: <20240416192736.90072-1-dm.chestnykh@gmail.com>

Hello Dmitry,

On Tue, 16 Apr 2024 22:27:36 +0300
Dmitry Chestnykh <dm.chestnykh@gmail.com> wrote:

> Linker process hangs if busybox was built with -g3,
> so fallback to -g2 in this case.
> The issue can be reproduced for example with
> qemu_aarch64_virt_defconfig by selecting BR2_DEBUG_3.
> 
> Signed-off-by: Dmitry Chestnykh <dm.chestnykh@gmail.com>

Thanks for your patch. However, this is more of a workaround than a
real fix, indeed the linker shouldn't hang at -g3.

Does this happen on all architectures? Does it happen regardless of the
compiler optimization level selected? Did you report the bug to
upstream binutils?

Thanks a lot,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-05-09 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 19:27 [Buildroot] [PATCH] package/busybox: Fallback to -g2 in if -g3 is enabled Dmitry Chestnykh
2024-05-09 14:33 ` Thomas Petazzoni via buildroot [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=20240509163345.4b91eca5@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dm.chestnykh@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.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.