`panic!` in repl on incomplete `db_add`

[duesee]

Just reporting what I stumble upon... sn0int looks super awesome so far! :-)

$ RUST_BACKTRACE=1 ./target/release/sn0int --workspace test repl
:: sn0int v0.26.0 lua repl
Assign variables with `a = sn0int_version()` and `return a` to print
Read the docs at https://sn0int.readthedocs.io/en/stable/reference.html

> db_add
thread 'main' panicked at library/core/src/panicking.rs:155:5:
attempted to leave type `&mut hlua_badtouch::Lua<'_>` uninitialized, which is invalid
stack backtrace:
   0: rust_begin_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_nounwind_fmt::runtime
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:110:18
   2: core::panicking::panic_nounwind_fmt
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:122:9
   3: core::panicking::panic_nounwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:155:5
   4: sn0int::repl::Repl::exec
   5: sn0int::repl::Repl::run
   6: sn0int::repl::run
   7: sn0int::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread caused non-unwinding panic. aborting.
[1]    85104 IOT instruction (core dumped)  RUST_BACKTRACE=1 ./target/release/sn0int --workspace test repl

---

Versions

• rustc 1.76.0 (07dca489a 2024-02-04)
• cargo 1.76.0 (c84b36747 2024-01-18)
• sn0int 0.26.0 (commit 77c5e3e11599b8d747b1333ffd3cb25116807442)
• Linux 6.6.10-76060610-generic #202401051437~1704728131~22.04~24d69e2 SMP PREEMPT_DYNAMIC Mon J x86_64 x86_64 x86_64 GNU/Linux

Environment

• PopOS!
• Current git checkout, compiled with --release