Index | Thread | Search

From:
Kirill A. Korinsky <kirill@korins.ky>
Subject:
Re: ungoogled-chromium-124.0.6367.207 quite unstable
To:
OpenBSD ports <ports@openbsd.org>
Date:
Fri, 24 May 2024 12:33:00 +0100

Download raw body.

Thread
oops,

I've forgot to add an example of stacktrace:

  (gdb) bt f
  #0  0x00000a7685192a01 in ?? ()
  No symbol table info available.
  #1  0x00007d27dbe62450 in ?? ()
  No symbol table info available.
  #2  0x0000000000040000 in ?? ()
  No symbol table info available.
  #3  0x00007d27dbe623b0 in ?? ()
  No symbol table info available.
  #4  0x00000a7685192a1d in ?? ()
  No symbol table info available.
  #5  0x00007d27dbe62570 in ?? ()
  No symbol table info available.
  #6  0x00000a768100bac5 in ?? ()
  No symbol table info available.
  #7  0x00000a78ffcdebe0 in ?? () from /usr/lib/libc.so.100.1
  No symbol table info available.
  #8  0x00000a78ffcdf3e8 in malloc_lock () from /usr/lib/libc.so.100.1
  No symbol table info available.
  #9  0x00000a78ffcdebe0 in ?? () from /usr/lib/libc.so.100.1
  No symbol table info available.
  #10 0x0000000000000020 in ?? ()
  No symbol table info available.
  #11 0x00007d27dbe62660 in ?? ()
  No symbol table info available.
  #12 0x44625052b7f78e9f in ?? ()
  No symbol table info available.
  #13 0x0000000000000000 in ?? ()
  No symbol table info available.
  (gdb)

anyway, it's quite useless.

Thus, I've tried to disable WASM without any success.

-- 
wbr, Kirill