Derevtsov Konstantin

Yep i think better if feature for testing will be on `rustyline` side. But there is still a problem, that output observable by user and output observable by integration tests...

I encountered this bug too. Looks like this problem occurs because: 1) we create read operation (future) with socket fd link in it 2) we create read operation (by putting...

Thank you for participating! Could you please check: 1) does `next` work in console mode? 2) provide some code for the repro? (or is this behavior observed in any code?)...

hm, i'm test both repro in my dev pc (ubuntu 22.04 + rust 1.77) and it is worked fine. So can you provide your output of `dpkg -l | grep...

Interesting, is this error occures at first stack frame? I mean, may be a fast solve of this problem at bs side - just cut backtrace from libunwind at error...

I tried to reproduce at fresh Fedora 39 Rustc version 1.77.1 Libunwind version: ```sh dnf list installed | grep unwind libunwind.x86_64 1.7.0-0.2.rc2.fc39 @anaconda libunwind-devel.x86_64 1.7.0-0.2.rc2.fc39 @fedora ``` And looks like...

No problem, are you observe this behavior with libunwind or builtin unwinder (--no-default-features)?

Hi! No, I decided to postpone this feature to the 0.4 release (the next one is 0.3 with async, call and other new commands). Of course, I will be very...

Thanks for the idea! I have never used this functionality in GDB (because I didn’t know), I will definitely try to implement it in version 0.3.0

Thank @orhun , I think current integration is a good start too, but we need to do some improvements :) I'm going to create a draft PR in `binsider` for...