VisualGDB stopped working

Sysprogs forums Forums VisualGDB VisualGDB stopped working

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #8259
    bernardofca
    Participant

    I have used VisualGDB successfully on multiple projects and it suddenly stopped working.

    gdb complains about:

    gdb-set disassembly-flavor intel (I don’t think that this is the issue)

    and hangs on:

    target remote :59325

    I have verified that:

    1.  I have the last version of everything
    2. OpenOCD test is working OK
    3. I have the same problem with a simple new solution (blink LED)

    I am using VS2010, STM32F103 and ST-LINK V2

    It is likely trivial but I did not solve it yet!

    Here is the Log:
    <div>(gdb begin)
    VisualGDB is licensed to XXXXXX at YYYYY
    C:\SysGCC\arm-eabi\bin\arm-eabi-gdb.exe –interpreter mi C:\Users\bernard\Documents\Projects_PT\bt\trunk\ttyy/Debug/ttyy.elf
    -gdb-version
    =thread-group-added,id=”i1″
    ~”GNU gdb (GDB) 7.10.1\n”
    ~”Copyright (C) 2015 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \”show copying\”\nand \”show warranty\” for details.\n”</div>
    <div></div>
    <div></div>
    <div></div>
    <div>
    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”</div>
    <div></div>
    <div>
    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”</div>
    <div></div>
    <div>
    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”…\n”
    ~”Reading symbols from C:\\Users\\bernard\\Documents\\Projects_PT\\bt\\trunk\\ttyy/Debug/ttyy.elf…”
    ~”done.\n”
    ~”GNU gdb (GDB) 7.10.1\n”
    ~”Copyright (C) 2015 Free Software Foundation, Inc.\n”
    ~”License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html&gt;\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.  Type \”show copying\”\nand \”show warranty\” for details.\n”</div>
    <div></div>
    <div></div>
    <div></div>
    <div>
    ~”This GDB was configured as \”–host=i686-pc-mingw32 –target=arm-eabi\”.\nType \”show configuration\” for configuration details.”</div>
    <div></div>
    <div>
    ~”\nFor bug reporting instructions, please see:\n”
    ~”<http://www.gnu.org/software/gdb/bugs/&gt;.\n”
    ~”Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/software/gdb/documentation/&gt;.\n”</div>
    <div></div>
    <div>
    ~”For help, type \”help\”.\n”
    ~”Type \”apropos word\” to search for commands related to \”word\”.\n”
    ^done
    -list-features
    ^done,features=[“frozen-varobjs”,”pending-breakpoints”,”thread-info”,”data-read-memory-bytes”,”breakpoint-notifications”,”ada-task-info”,”language-option”,”info-gdb-mi-command”,”undefined-command-error-code”,”exec-run-start-option”]
    -gdb-set stop-on-solib-events 1
    ^done
    -gdb-set disassembly-flavor intel
    ^error,msg=”No symbol \”disassembly\” in current context.”
    -gdb-set print demangle off
    ^done
    -break-insert -f main
    ^done,bkpt={number=”1″,type=”breakpoint”,disp=”keep”,enabled=”y”,addr=”0x08000a32″,func=”main()”,file=”LEDBlink.cpp”,fullname=”C:\\Users\\bernard\\Documents\\Projects_PT\\bt\\trunk\\ttyy\\LEDBlink.cpp”,line=”14″,thread-groups=[“i1″],times=”0″,original-location=”main”}
    set remotetimeout 60
    &”set remotetimeout 60\n”
    =cmd-param-changed,param=”remotetimeout”,value=”60″
    ^done
    target remote :59395
    &”target remote :59395\n”
    &”:59395: The system tried to join a drive to a directory on a joined drive.\n”
    ^error,msg=”:59395: The system tried to join a drive to a directory on a joined drive.”
    mon halt
    &”mon halt\n”
    &”\”monitor\” command not supported by this target.\n”
    ^error,msg=”\”monitor\” command not supported by this target.”
    mon reset init
    &”mon reset init\n”
    &”\”monitor\” command not supported by this target.\n”
    ^error,msg=”\”monitor\” command not supported by this target.”
    load
    &”load\n”
    &”You can’t do that when your target is `exec’\n”
    ^error,msg=”You can’t do that when your target is `exec'”
    -data-evaluate-expression “sizeof(void *)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(int)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(short)”
    ^done,value=”2″
    -data-evaluate-expression “sizeof(long)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(long long)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(char)”
    ^done,value=”1″
    -data-evaluate-expression “sizeof(wchar_t)”
    ^error,msg=”No symbol \”wchar_t\” in current context.”
    -data-evaluate-expression “sizeof(float)”
    ^done,value=”4″
    -data-evaluate-expression “sizeof(double)”
    ^done,value=”8″
    -data-evaluate-expression “sizeof(long double)”
    ^done,value=”8″
    info target
    &”info target\n”
    ~”Symbols from \”C:\\Users\\bernard\\Documents\\Projects_PT\\bt\\trunk\\ttyy\\Debug\\ttyy.elf\”.\n”
    ~”Local exec file:\n”
    ~”\t`C:\\Users\\bernard\\Documents\\Projects_PT\\bt\\trunk\\ttyy\\Debug\\ttyy.elf’, file type elf32-littlearm.\n”
    ~”\tEntry point: 0x80002d8\n”
    ~”\t0x08000000 – 0x080001e4 is .isr_vector\n”
    ~”\t0x080001e4 – 0x08000b44 is .text\n”
    ~”\t0x08000b44 – 0x08000b48 is .init_array\n”
    ~”\t0x08000b48 – 0x08000b4c is .fini_array\n”
    ~”\t0x20000000 – 0x20000004 is .data\n”
    ~”\t0x20000004 – 0x20000024 is .bss\n”
    ^done
    -data-evaluate-expression “&_estack”
    ^done,value=”0x2000c000 <error: Cannot access memory at address 0x2000c000>”
    -var-create – * “*((void **)0x2000bffc)”
    ^done,name=”var1″,numchild=”0″,value=””,type=”void *”,has_more=”0″
    -var-evaluate-expression “var1″
    ^done,value=””
    -exec-continue
    ^error,msg=”The program is not being run.”</div>

    • This topic was modified 8 years, 6 months ago by bernardofca.
    • This topic was modified 8 years, 6 months ago by bernardofca.
    #8264
    support
    Keymaster

    Hi,

    Please check the OpenOCD window for errors. There was a bug in our recent OpenOCD release that could have caused it and it was fixed in VisualGDB 5.1r6.

    Please upgrade to that version or alternatively re-download the latest OpenOCD debug package via Embedded Tools Manager. Then open the Debug Settings page, change any setting there and press “OK”. This should fix the problem.

    #8268
    bernardofca
    Participant

    Thanks for the weekend support. I tried all the suggestions and it still does not work.

    I tried to re-install everything on a virgin PC and it worked (used the trial version of VisualGDB).

     

    Something is obviously corrupted on my PC but I don’t know what. I tried to transfer the working solution and it still fails.

     

    What else should I try?

     

    #8269
    bernardofca
    Participant

    Additional information: my setup works with the Texane debugger but not with OpenOCD. I have erased and downloaded Open OCD multiple times w/o success.

    #8273
    support
    Keymaster

    OK, then please post the contents of the OpenOCD window in Visual Studio here so that we could help you figure out what is causing the problems.

    #8274
    bruno
    Participant

    hi, try to iniciate your IDE with adminstrator permission: right click on ide’s icon > execute with adminstrator (or somethinhg like that).

     

    #8275
    bernardofca
    Participant

    All: thanks for the support.

    In the process of trying everything, I removed VisualGDB, erased all the registry entries containing the magic word, erase all directories, etc

    After yet another reboot, I got it back!

    I am willing to forget the 2 days of work I lost, if I know how to quickly reverse this situation if it happens again!

    #8276
    support
    Keymaster

    Most likely while deleting and reinstalling everything you installed the new version of the debug package that includes the fix as we suggested above.

    Now that you have the latest version installed, the problem should not occur anymore.

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