why rust?

hate loading times? rust is as C++ fast and unfortunately not easier to program than “user friendly” as C++

(from src): Performance: Fast and memory-efficient, suitable for critical services, embedded devices, and easily integrated with other languages.

  • Reliability: Our rich type system and ownership model ensure memory and thread safety, reducing bugs at compile-time.

  • Productivity: Comprehensive documentation, a compiler committed to providing great diagnostics, and advanced tooling including package manager and build tool (Cargo), auto-formatter (rustfmt), linter (Clippy) and editor support (rust-analyzer).

why the name?

why the dirty name? usually users associate rust with metal that is broken down by oxygen into not-so-usefull dirt

“named it Rust, after a group of remarkably hardy fungi that are, he says, “over-engineered for survival”” (src)

#WOW! need a rust ebook? (git clone https://github.com/goldcoders/Rust.git)

“Basically, rust-gdb is a wrapper that loads external Python pretty-printing scripts into GDB. This is useful (and somewhat necessary) when debugging more complex Rust programs because it significantly improves the display of Rust data types.” (src)

what the developer has to do:

hostnamectl; # tested on
   Static hostname: lenovo
  Operating System: Debian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.0-17-amd64
      Architecture: x86-64

setup rust like in this article

# test that paths are working
rustc --version
rustc 1.53.0 (53cb7b09b 2021-06-17)

# create new project with cargo
cargo new helloworld
cd ./helloworld/src
cargo build
 Finished dev [unoptimized + debuginfo] target(s) in 0.00s
cargo run
 Finished dev [unoptimized + debuginfo] target(s) in 0.00s
Running `/home/devrust2/helloworld/target/debug/helloworld`
Hello, world!

vim main.rs
# within vim
:packadd termdebug
:let termdebugger="rust-gdb"
:Termdebug

# now this should show up

congrats! ready to debug 🙂

within gdb:

# load the compiled binary with symbols

file ../target/debug/helloworld
# then the developer is ready to start
start

# hurray! :) step debugging works :)

video with music:

 

creditz:

go to: https://alpha2phi.medium.com/setting-up-neovim-for-rust-debugging-termdebug-and-vimspector-df749e1ba47c

Rust-Links:

via rss:

PDFs:

GDB Cheat Sheet.pdf

PS: Conque-GDB vim plugin can (probably) enable rust and c++ setp debugging in vim prior to v.8.1 too, but it was not updated since 2016 and throws errors.

 

Videos:

https://youtu.be/iVYWDIW71jk

liked this article?

  • only together we can create a truly free world
  • plz support dwaves to keep it up & running!
  • (yes the info on the internet is (mostly) free but beer is still not free (still have to work on that))
  • really really hate advertisement
  • contribute: whenever a solution was found, blog about it for others to find!
  • talk about, recommend & link to this blog and articles
  • thanks to all who contribute!
admin