Moved: Reply To: Analyze performance – Debugging Failed – gdbserver exited with code 1

Sysprogs forums Forums VisualGDB Moved: Reply To: Analyze performance – Debugging Failed – gdbserver exited with code 1

This topic contains 1 reply, has 2 voices, and was last updated by  support 1 month ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #22666

    alex778801
    Participant

    Hello!

    I have exactly the same problem. Setting Tools->Options->VisualGDB->General->Profiling->Delay before starting valgrind’s vgdb tool to 5000 provides to run, but NOTHING TESTING

    Have you got a soulition?

    #22688

    support
    Keymaster

    Hi,

    We would advise running a few quick experiments to understand what components could be causing this:

    • Try profiling a “hello, world” program with VisualGDB.
    • If it doesn’t work, try running valgrind manually (let us know if you need help with command lines).
    • It the “hello, world” works, try running valgrind manually with your program.

    If it looks like the problem is between valgrind and your specific project, please try simplifying it (e.g. removing some sources/libraries/optimization settings). If the problem occurs with VisualGDB, but doesn’t occur otherwise, it’s likely caused by some arguments VisualGDB is using. In this case please try comparing the command lines that work and the command lines used by VisualGDB (from View->Other->VisualGDB Diagnostics Console).

    If you need further help at any step, don’t hesitate to get back to us.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.