Core-sqlx-sqlite-wor

Help
1

Hello. I have installed Atuin CLI on a Unix machine, following the recommended installation approach. Atuin seems to work normally but it creates files with a name starting with `core-sqlx-sqlite-wor`, for example core-sqlx-sqlite-wor-112472-7, every now and then. The files are created in the current directory. I am not sure what triggers the creation of the file: it is not every time I use the command history. Any idea what could cause this?

2

It crashed somehow and generated a coredump for inspection (with e.g. gdb).

3

Could you share some more info please? What kind of unix machine?

The output of “atuin doctor” would also be super helpful!

4

Here is the output of atuin doctor (I see it includes the description of the Unix machine):

$ atuin doctor
Atuin Doctor
Checking for diagnostics


Please include the output below with any bug reports or issues

{
  "atuin": {
    "version": "18.14.1",
    "commit": "1e93b3129bc540ae8d2b996ba6aa64b93a732d99",
    "sync": {
      "auth_state": "Hub (authenticated)",
      "records": true,
      "auto_sync": true,
      "last_sync": "2026-04-16 18:39:54.841347951 +00:00:00"
    },
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "bash",
    "default": "bash",
    "plugins": [
      "atuin",
      "blesh",
      "bash-preexec"
    ],
    "preexec": "blesh-0.4.0-nightly+32bb63d"
  },
  "system": {
    "os": "Red Hat Enterprise Linux",
    "arch": "x86_64",
    "version": "9.6",
    "disks": [
      {
        "name": "/dev/sdb31",
        "filesystem": "xfs"
      },
      {
        "name": "/dev/sdb11",
        "filesystem": "ext4"
      },
      {
        "name": "/dev/sdb61",
        "filesystem": "ext4"
      },
      {
        "name": "/dev/sdb21",
        "filesystem": "vfat"
      },
      {
        "name": "10.101.0.1@o2ib2:10.101.0.3@o2ib2:10.101.0.2@o2ib2:10.101.0.4@o2ib2:/fshomisc/home",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.1@o2ib2:10.101.0.3@o2ib2:10.101.0.2@o2ib2:10.101.0.4@o2ib2:/fshomisc/log",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.1@o2ib2:10.101.0.3@o2ib2:10.101.0.2@o2ib2:10.101.0.4@o2ib2:/fshomisc/sup",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.1@o2ib2:10.101.0.3@o2ib2:10.101.0.2@o2ib2:10.101.0.4@o2ib2:/fshomisc/sys",
        "filesystem": "lustre"
      },
      {
        "name": "10.100.11.1@o2ib,10.100.11.1@o2ib1:10.100.11.2@o2ib,10.100.11.2@o2ib1:10.100.11.3@o2ib,10.100.11.3@o2ib1:10.100.11.4@o2ib,10.100.11.4@o2ib1:/fsn1",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.20@o2ib2:10.101.0.22@o2ib2:10.101.0.21@o2ib2:10.101.0.23@o2ib2:/fswork",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.20@o2ib2:10.101.0.22@o2ib2:10.101.0.21@o2ib2:10.101.0.23@o2ib2:/fsnomig",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.36@o2ib2:10.101.0.38@o2ib2:10.101.0.37@o2ib2:10.101.0.39@o2ib2:/fsstor",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.36@o2ib2:10.101.0.38@o2ib2:10.101.0.37@o2ib2:10.101.0.39@o2ib2:/fsmig",
        "filesystem": "lustre"
      },
      {
        "name": "10.101.0.60@o2ib2:10.101.0.61@o2ib2:10.101.0.62@o2ib2:10.101.0.63@o2ib2:/fsmisc",
        "filesystem": "lustre"
      }
    ]
  }
}
5

I have looked at the core file with gdb. Here is what I obtain:

(gdb) core-file core-sqlx-sqlite-wor-1720176-7
[New LWP 1720892]
[New LWP 1720188]
[New LWP 1720181]
[New LWP 1720332]
[New LWP 1720349]
[New LWP 1720727]
[New LWP 1720376]
[New LWP 1720176]
[New LWP 1720354]
[New LWP 1720355]
Missing separate debuginfo for the main executable file.
The debuginfo package for this file is probably broken.
Core was generated by `atuin history end --exit 0 --duration=49366000 -- 019d9797ad967152b11294285419b'.
Program terminated with signal SIGBUS, Bus error.
#0  0x000014cd86f356d0 in ?? ()
[Current thread is 1 (LWP 1720892)]

Is this helpful?

6

Without debug symbols it is not very useful. It shows the command line, and the direct reason to crash is SIGBUS. That’s it. Try type bt and Enter at the (gdb) prompt you may see the call stack, or maybe more ?? lines.

The core file indicates that the SQLite thread is the crashing thread. Maybe something is wrong with SQLite which seems to bundled.

7

Here is the output of backtrace in gdb:

(gdb) bt
#0  0x000014cd86f356d0 in ?? ()
#1  0x000014cd86fffabe in ?? ()
#2  0x0000000000000000 in ?? ()
8

Is there a way to install a version of atuin with debuginfo included?