-
-
Notifications
You must be signed in to change notification settings - Fork 37
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looking forward to RTT and GDB at the same time.
I only have some minor comments.
.as_deref() | ||
.or_else(|| Some("localhost:1337")); | ||
// This next unwrap will always resolve as the connection string is always Some(T). | ||
log::info!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the reason for this change? Is there a threading issue with the logging::println
call?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this writes into the RTTUI, messing with the entire layout, rendering RTT unusable :/ I have not fond a way to swallow the logs from the GDB thread yet :/
Currently the GDB server also emits a lot of warnings that maybe should be debug logs. We sould clean this up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
bors r+ |
159: Allow RTT & GDB to run concurrently! r=Yatekii a=Yatekii Co-authored-by: Noah Hüsser <[email protected]> Co-authored-by: Noah Hüsser <[email protected]> Co-authored-by: Yatekii <[email protected]>
Build failed: |
bors r+ |
Build succeeded: |
Since probe-rs#159 it has been possible to use RTT and GDB at the same time.
259: Remove mutual exclusion comment on RTT / GDB r=Yatekii a=robyoung Since #159 it has been possible to use RTT and GDB at the same time. Co-authored-by: Rob Young <[email protected]>
No description provided.