Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Jul 2021 06:20:41 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Willem Jan Withagen <wjw@digiware.nl>
Cc:        Tobias Kortkamp <tobik@freebsd.org>, freebsd current <freebsd-current@freebsd.org>,  Dimitry Andric <dim@freebsd.org>
Subject:   Re: Changes to backtrace() ??
Message-ID:  <CANCZdfqjn9n=2eBfNB8LT9u_cA6%2BjRp2dYV52MC1sZnG5=mmig@mail.gmail.com>
In-Reply-To: <1cd06d37-7a20-dfd0-13df-af79be0672d8@digiware.nl>
References:  <73332c15-d597-0dee-4af8-1c11101a8aef@digiware.nl> <YN7ny0jQT3Y8D/38@urd.tobik.me> <1cd06d37-7a20-dfd0-13df-af79be0672d8@digiware.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000009f5aae05c622fc2c
Content-Type: text/plain; charset="UTF-8"

On Fri, Jul 2, 2021, 4:35 AM Willem Jan Withagen via freebsd-current <
freebsd-current@freebsd.org> wrote:

> On 2-7-2021 12:17, Tobias Kortkamp wrote:
> > On Fri, Jul 02, 2021 at 11:52:14AM +0200, Willem Jan Withagen via
> freebsd-current wrote:
> >> Hi,
> >>
> >> Have there been changes in the backtrace() calls?
> >> I recently upgraded my current server, and now the Ceph backtrace test
> >> starts to fail....
> >>
> >> It looks like it is implemented in the llvm code.
> >> So it could be that something is off in that code.
> > lang/rust also fails to build on at least aarch64 after the LLVM12
> > import (the prebuilt bootstrap crashes).  Very similar backtrace.
> > See https://bugs.freebsd.org/256864
> Yup,
> That trace looks very similar.
>
> Forgot to explicitly mention that my problem is with a very recent 14.0
> FreeBSD quad-b.digiware.nl 14.0-CURRENT FreeBSD 14.0-CURRENT #1
> main-n247587-33b8c039a96: Sun Jun 27 21:19:03 CEST 2021
> root@quad-b.digiware.nl:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
> amd64
>

That is after the last LLVM import.  I've cc'd dim@.

Warner

The one before that was from around early May, and that did not have the
> problem...
> I have a Jenkins builder/tester that checks all changes that get submitted.
> And only after the upgrade last weekend things started to go wrong.
>
> But I do not track changes to current so I have no clue as to what has
> changed there.
>
> --WjW
>
>
>

--0000000000009f5aae05c622fc2c--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqjn9n=2eBfNB8LT9u_cA6%2BjRp2dYV52MC1sZnG5=mmig>