语言

Menu
Sites
Language
Apparent compiler and/or runtime bug: where to report?

Using the latest public bits (VS2017 15.8.5, VS Tools for Tizen 1.5.0.0,  Wearable (Preview) package 0.0.38) , testing on a real Galaxy Watch (SM-R800, Tizen Version 4.0.0.0, Software version R800XXU1BRH3)), when I run this code:

            int result = 0;
            sbyte[] v = {  -1 };

            result |= (v[0] & 0x000000FF);
            log.WriteLine("Result using array element is " + result);

            result = 0;
            sbyte v3 = -1;
            result |= (v3 & 0x000000FF);
            log.WriteLine("Result using variable is " + result);

I get:

Result using array element is -1
Result using variable is 255

When I use the same code on Windows using .NET Core, I get 255 in both cases.  It seems like a bug ... where should I report this?

Thanks,

   Damian

 

列表

响应

7 回复
Armaan-Ul- Islam

Hello Damian,

It seems, I'm getting 255 in both cases.

 

My Reproduction path: File > New > Project > Tizen App (Tizen. NUI) > filename.cs > Paste your snippet > Check @ Watch window while Debugging..

Damian Mehers

Hi,

Have you tried on a real device?  I'm not able to get the debugger working on a real device (would appreciate pointers on how to get it running!).

I've reported it in the .NET CLR Github issues and it seems to be a regression: https://github.com/dotnet/coreclr/issues/20102

Damian Mehers

The differing result (when targeting arm) seems to  depend on whether the runtime target framework is configured to 2.0 or 2.1.  When I set it to 2.1 my code runs fine on a real device.

Armaan-Ul- Islam

Thanks for sharing the solution on this thread, might help out developers on this Forum.

Armaan-Ul- Islam

Would you please share the step by step procedure of how you got the debugger working on a real device? along with the process to change the runtime target framework.

Hafner

Actually, I got the same issue with Visual Studio - cannot debug on a real device. Actually I cannot even upload the tpk to the real device from Visual Studio but use sdb on command line separately (with the same parameters indeed). So not sure why Visual studio fails - VS actually starts and finish the upload but the difference is that the binary simply cannot be started when deployed throu VS - the very same tpk works just fine when uploaded manually throu SDB on cmd.

Armaan-Ul- Islam

I've tested on my environment, Seems the case is same here. Can't Debug Tizen app on real device.

 

I would suggest you to report an Issue on 'Tizen VS Extension tool repository', we might receive a response from them.

In addition, You may report a bug on Tizen bug Tracker. Here’s a guideline on how to report bugs. Please share your progress and the 'Reported bug' link here on this post to help the developers keep track.