• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 55 subscribers
  • Views 919 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSv5.1.0.07001 collapses multi-level expressions in Expression Watch Window

MikeH
Guru 15580 points


CCS seems to automatically collapse all expanded expressions in the watch window when you return from a function call. Irritating....:(

 

  • 0
    TI__Guru*** 130875 points

    Hi Mike,

    I can confirm what you see.  Let me see if there is an option or setting for this.  That I am aware of there is not but I will try to confirm.

     

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Guru*** 130875 points

    Hi Mike,

    There is unfortunately, as thought, no way to change this behaviour.

    I have filed this in our system as a potential enhancement.  This is the number and the link contains the information you need to track it if you wish.

     

     

    SDSCM00041843

     

    http://processors.wiki.ti.com/index.php/Compiler_Defects_Database

    I hope this clarification helps.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Guru 15580 points

    Lisa,

    Lisa TI said:
    no way to change this behaviour.

    That *is* unfortunate. This is a serious problem for serious debugging. I could understand it the expression was "local" and you exited the context of the expression that i would close. But these are globals. They should remain open all sections of code.

    When do you think this might get incorporated?

    Thx,

    MikeH

     

  • 0 in reply to MikeH
    TI__Guru*** 130875 points

    Hi Mike,

    I can not say or make any guaratees.  I have submitted it as a potential enhancement and hopefully it will be something that comes and quickly.

    You can follow the submission using the number and link I put in my previous post.   You will be able to see the status updates etc.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Guru 20045 points

    Hello,

    It has been almost 4.5 years since the last post in this thread.  Is this issue going to be fixed in the next revision?  I would consider this issue more towards the major side than minor.  It doesn't exactly stop me from doing my work, but it does slow me down considerably.

    Stephen

  • 0 in reply to stevenh
    TI__Guru**** 472381 points
    Hi Stephen,
    41843 has been marked as a duplicate of 40999, which is classified as a "major" issue. There is a dependency on open source changes from the Eclipse community. That is the last update I see for this issue. I'll try to see if there has been any progress on this.

    Thanks
    ki
  • 0 in reply to Ki
    Guru 20045 points

    Ok, I couldn't find 40999.

    I'll wait for you reply.

    Thanks,

    Stephen

  • 0 in reply to stevenh
    TI__Guru**** 472381 points
    40999 was filed as an "internal" issues, hence it is not visible on out external portal.

    However, related issue 51319 should be visible through the external portal. Instead of waiting around for the Eclipse community to fix it, the CCS team has taken the ball to find a way to address this without changes from the community.

    This one has been committed to the 6.2.0 release in May time frame.

    Thanks
    ki
  • 0 in reply to Ki
    Guru 20045 points
    Fantastic.
    Just to let you know, I couldn't find SDSCM00051319 either.
    Thanks,
    Stephen
  • 0 in reply to stevenh
    TI__Guru**** 472381 points
    oops... yes i see now that it is mark as internal also. Sorry. But I can confirm that it is committed to 6.2.0.