Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. GDB Not Working with configuration set to "Debug"
Forum Updated to NodeBB v4.3 + New Features

GDB Not Working with configuration set to "Debug"

Scheduled Pinned Locked Moved Installation and Deployment
2 Posts 2 Posters 2.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    blissfreak
    wrote on last edited by
    #1

    Hi, I'm running Windows 7, 64 bit, with MinGW (4.4 - the default that comes with the QtSDK), and have all of my components updated to their latest version.

    Unfortunately, the pythongdb .exe won't recognize my breakpoints. The debugger will simply stall for a minute or so after the program has run. I'm not getting any segmentation faults, or anything, but I need to desperately debug my application.

    What could be the issue here? Is there anything I can post?

    Compiler Output

    @
    18:23:59: Running build steps for project eng-optimo...
    18:23:59: Configuration unchanged, skipping qmake step.
    18:23:59: Starting: "C:\QtSDK\mingw\bin\mingw32-make.exe"
    C:/QtSDK/mingw/bin/mingw32-make.exe -f Makefile.Debug
    mingw32-make.exe[1]: Entering directory C:/Users/Holland/Documents/code/git/virtual-engine/eng-optimo/MinGW_Debug' mingw32-make.exe[1]: Nothing to be done for first'.
    mingw32-make.exe[1]: Leaving directory `C:/Users/Holland/Documents/code/git/virtual-engine/eng-optimo/MinGW_Debug'
    18:23:59: The process "C:\QtSDK\mingw\bin\mingw32-make.exe" exited normally.
    @

    .pro File

    @
    CONFIG += qt console
    QT += core gui

    #QMAKE_CXX_FLAGS += -std=c++0x

    QMAKE_CXXFLAGS += -std=c++0x -g

    SOURCES +=
    main.cpp
    ViMain.cpp
    ViShape.cpp
    ViCube.cpp
    ViShader.cpp
    ViBufferObject.cpp
    ViGraphicsTesting.cpp
    ViGlut.cpp
    ViEngine.cpp

    HEADERS +=
    StdAfx.h
    ViMain.h
    ViShape.h
    ViCube.h
    ViShader.h
    ViBufferObject.h
    ViGraphicsTesting.h
    ViGlut.h
    ViEngine.h

    win32:LIBS += -lopengl32 -lglu32 -lfreeglut -lglew32 -lSDL
    unix:LIBS += -lGL -lGLU -lglut -lGLEW -L/usr/lib/libpng12.so -lSDL
    @

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobias.hunger
      wrote on last edited by
      #2

      What does the debugger log (top right area of the debug mode IIRC) say?

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved