Search Unity

Debugging in monodevelop : can't watch vector3

Discussion in 'Linux' started by matrem, Dec 9, 2016.

  1. matrem

    matrem

    Joined:
    Jan 25, 2013
    Posts:
    12
    Hello,

    I can't watch a specific vector3 correctly in monodevelop debugger. (I can't see others correctly)
    A Debug.Log give a correct print though.
    Even for a Vector3 test = new Vector3(0, 0, 1); Watching it give me a zero vector...
    I in a function called from a FixedUpdate().

    Anybody experiencing this? Is there a workaround?

    I use unity 5.5.0xf3 and monodevelop 5.9.6, under kubuntu 16.10.
    Is It possible that it's due to a morning update about libc?
     
    matrem, Dec 9, 2016
    #1

  2. matrem

    matrem

    Joined:
    Jan 25, 2013
    Posts:
    12
    None of these change something :
    - rebooting
    - cleaning project (Library, sln. csproj, ...)
    - reinstalling 5.5
    - removing monodevelopp 5.10 (another version installed)

    I'll try reinstalling 5.4
     
    matrem, Dec 9, 2016
    #2

  3. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,938
    We're not aware of that issue, but it sounds like a bug on the Unity side. Can you submit a bug report with the project to reproduce this?
     
    JoshPeterson, Dec 9, 2016
    #3

  4. matrem

    matrem

    Joined:
    Jan 25, 2013
    Posts:
    12
    In 5.4 it seems ok.
    But reverting a project from 5.5 to 5.4 seems not ok at all :p (many gameobject name reseted to "", many game object disabled...)
     
    matrem, Dec 9, 2016
    #4

  5. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,938
    It seems there is a regression bug in 5.5 for sure then. If you can provide a bug report with a repro project, we would appreciate it!
     
    JoshPeterson, Dec 9, 2016
    #5

  6. matrem

    matrem

    Joined:
    Jan 25, 2013
    Posts:
    12
    Ok bug reported (with the simpler scene ever :)).
    Actually watching the vector3 realy set it up to zero (the next debug.log will print zero).
    A strange quantic bug...
     
    matrem, Dec 9, 2016
    #6

  7. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,938
    Thanks. Can you let me know the bug number?
     
    JoshPeterson, Dec 9, 2016
    #7

  8. matrem

    matrem

    Joined:
    Jan 25, 2013
    Posts:
    12
    Of course : 859821
     
    matrem, Dec 9, 2016
    #8

  9. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,938
    Thanks!
     
    JoshPeterson, Dec 9, 2016
    #9

  10. matrem84

    matrem84

    Joined:
    Feb 3, 2017
    Posts:
    5
    My bug has been closed. It seems it can't be reproduced by the development team.

    So I try a fresh install of another distribution : linux mint 18.1 (64bits), with unity 5.5.1. => My problem is always there.

    Is there really nobody able to reproduce this problem?
    Can it be due to my not so recent hardware (intel quad core q6600) ?

    For now I have two choices : debugging with Debug.Log or staying on 5.4... It's a bit frustrating :'(
     
    matrem84, Feb 3, 2017
    #10

  11. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,938
    I did talk to the QA team about reproducing it. I'm not sure why we cannot. I suspect the problem happens in Unity 5.5 because we upgraded the Mono C# compiler. The new compiler generates sequence points in the .mdb files differently than the old compiler. These sequence points are used by the debugger to determine where to allow break points and single stepping.

    I don't think it would be related to older hardware. At least, similar bugs to this one have not been dependent on specific hardware. But then again, we can usually reproduce them.

    Unfortunately I don't have a good solution for you now. If we cannot reproduce the issue, we cannot fix it, or even suggest a workaround.

    I guess that Debug.Log is the best (bad) option for now.
     
    JoshPeterson, Feb 3, 2017
    #11

  12. matrem84

    matrem84

    Joined:
    Feb 3, 2017
    Posts:
    5
    Bug always present on my current pc with 2017.1.0xf1.
    (linux mint 18.1 cinamon 64 bit kernel 4.8.0-56 core 2 quad gtx 960)
     
    matrem84, Jun 28, 2017
    #12

  13. matrem84

    matrem84

    Joined:
    Feb 3, 2017
    Posts:
    5
    I change my pc to a most modern one (core i7)
    WIth a more recent version of linux linux lint 18.2 Cinnamon 64 bits, kernel 4.10.0-35
    And the last stable version of unity 2017.1.1xf1.
    Always the same problem :
    http://mathieuroumillac.free.fr/out.mp4
     
    matrem84, Sep 21, 2017
    #13