Thursday, April 19th 2018, 11:24pm UTC+2

You are not logged in.

  • Login
  • Register

c0dy

Beginner

Date of registration: Feb 21st 2018

Posts: 1

1

Tuesday, March 13th 2018, 2:36pm

Rust support in Ozone?

I used Ozone with a Rust program on a STM32 and my expierience was not really good.
Most time it looks like Ozone can not relate source to machine code at all. (I thought debugging info ist language independent?)
Also it does not recognise the Rust data types in the watch window.

Is there any Rust support planned? That would be great!

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 931

2

Wednesday, March 14th 2018, 3:58pm

Hello,

Thank you for your inquiry.
Ozone is a C/C++ debugger. Other programming languages might work but it is not guaranteed.

Quoted

Also it does not recognise the Rust data types in the watch window.

This is quite possible as Ozone does not handle Rust specific data types.

Quoted

Is there any Rust support planned? That would be great!


Currently there are no plans to do so.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Date of registration: Feb 23rd 2018

Posts: 6

3

Tuesday, March 27th 2018, 12:13pm

We also (in my company) use Rust and Ozone as a debugger.

It is true, watch data types and watch expression are not supported, however the rest seems fine. Ozone seems to have trouble recognizing data types sizes.

The Global/Local Data successfully recognizes rust variables. If you want to check the value of the data you have to right click and check the variable value in the memory browser itself.

You can also recognize rust functions and files in the source and function viewer.

I suppose this all work because in the end the debug symbols are pretty much language abstract.

Alessandro