No debug info on C-style unnamed structures

Sysprogs forums Forums VisualGDB No debug info on C-style unnamed structures

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #682
    Anonymous
    Participant

    It seems that VisualGDB incorrectly interprets information about structures defined in C-style. If some structure contains unnamed structure as a first member, then no debug information will be provided.

    At the same time in GDB Session it is possible to retrieve information manually.

    
    p st
    &"p stn"
    $1 = {{member1 = -139589008
    , member2 = -1 '377'
    }
    , member6 = 4196992
    }
    #2775
    ket
    Participant

    Hi,

    When you hover over st, what is VisualGDB calling from gdb and what is its response (also in the GDB Session window)? Is it the same as the command you run manually?

    #2774
    Anonymous
    Participant

    Hello,

    I got following interaction log (hovered on st, then expanded):

    
    -var-create --frame 0 --thread 1 - * "st"
    ^done,name="var2",numchild="1",value="{...}",type="MyStruct",thread-id="1",has_more="0"
    -var-list-children --simple-values "var2" 0 1
    ^done,numchild="1",children=[child={name="var2.public",exp="public",numchild="2",value="",thread-id="1"}],has_more="0"
    -var-list-children --simple-values "var2.public" 0 2
    ^done,numchild="2",children=[child={name="var2.public.",exp="",numchild="1",type="struct {...}",thread-id="1"},child={name="var2.public.member6",exp="member6",numchild="0",value="4196992",type="int",thread-id="1"}],has_more="0"
    -var-list-children --simple-values "var2.public" 0 2
    ^done,numchild="2",children=[child={name="var2.public.",exp="",numchild="1",type="struct {...}",thread-id="1"},child={name="var2.public.member6",exp="member6",numchild="0",value="4196992",type="int",thread-id="1"}],has_more="0"
    

    By the way the same issue affects Watch and Auto windows.

    #2776
    support
    Keymaster

    Hi,

    We have looked into it and added a workaround to VisualGDB 4.1r7. Please note that you can also resolve this issue by updating your GDB to 7.6.

    #2777
    Anonymous
    Participant

    Hello,

    Thank you for fast turnaround! Both solutions worked for me.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.