Conversation
jarkko

Jarkko Sakkinen

Memory safety is somewhat relative. My very early C version of the tracker has segfaulted maybe 1-2 times. Rust had much more memory instability.

Why C version is more stable:

1. If there is a segafault in a C program, for user space program, the full disclosure of the bug takes me like less than 20 minutes, with or without symbols. The binary is simple and as per code generated C is the most WYSIWYG language ever.
2. I can go absolutely sick in QA torture of the executable. There's so many ways you can bomb a C binary and trace everything in eBPF detail if you want, you can symbolic execute it with clang-tidy, Valgrind it etc.

I.e. while there are no federated laws the net result is still favorable for C at least in this project. I'm glad I started this rewrite :-)
1
0
1
penguin42@mastodon.org.uk

penguin42

Reply to @jarkko

@jarkko how did you manage to make your Rust code have memory instability?

1
0
0
jarkko

Jarkko Sakkinen

Reply to @penguin42@mastodon.org.uk
Maybe I suck :-) I don't know.
2
0
0
jarkko

Jarkko Sakkinen

Reply to @jarkko
@penguin42 And could be also my limited Rust debugging skills compared to C but yeah it is my leisure time project, so I use C, which I enjoy the most :-)
0
0
0
penguin42@mastodon.org.uk

penguin42

Reply to @jarkko

@jarkko Nah! It seems pretty hard to break memory instability in Rust (without unsafe's); I'm still learning Rust though but I'm using it for anythign where I'm writing new stuff to try and learn it.

1
0
1
jarkko

Jarkko Sakkinen

Reply to @penguin42@mastodon.org.uk
@penguin42 This is true and better debugging skills would probably enable me to locate the failing crate :-)
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: