Rust, RR, Neovim: A perfect debug combination

Post by planede » Wed, Apr 12, 2023, 8:20 AM UTC

cowl wrote: post #85

planede wrote: post #31

Earlier quoted context omitted.

I started watching [3]. I have no stakes in this, but a lot of stuff I should be enraged about... I'm just not? Doesn't look fundamentally different to Debian or Firefox trademark policies. I guess it is an abrupt change in trademark enforcement for Rust.

Don't look fundamentally different? May I'm missing something but I have not seen a single tutorial or article about something Debian or Firefox that starts that with the disclaimer "This is not affiliated with the official Debian etc" Like the R** Foundation is asking to. Let's not even mention the unreasonables of not being able to name package writen in R** as package-rust.=, somethng that no other programing lang…

Go ahead and write a tutorial about Rust without a disclaimer. This is totally non-enforceable, trademarks can't limit talking about the thing. As long as it's clear that you are not representing them, it's fine, even without a disclaimer as described in their policy.

IANAL and this is not legal advise, but I wouldn't sweat about it. This same thing applies to any other trademark too, be it Debian, Firefox, Nintendo or Coca-Cola.

Post by roca » Thu, Apr 13, 2023, 7:38 AM UTC

thegeomaster wrote: post #32

ObscureScience wrote: post #10

Earlier quoted context omitted.

Is that true? I genuinly have no experience with it. In their example they debug Firefox which I would consider a big application. Of course there are many levels above, and maybe you are talkning about tens of GB of memory usage?

I haven't tried with FF personally, but the issue I have is that the traces are huge and reverse execution through memory-intensive codepaths takes a very long time, making the experience really slow. Or you can run a release build (with optimizations), in which case everything gets inlined, your asserts get nuked, and you're unable to inspect state well enough to figure out what's going on. In most cases, an ordinar…

Please file an rr issue and tell us more about your situation.

Memory size and traffic shouldn't really be a problem. Multicore parallelism is the main problem. I've used rr with some very memory-hungry apps with good results.

Re: Rust, RR, Neovim: A perfect debug combination

Re: Rust, RR, Neovim: A perfect debug combination