Summary: | gdb can't find source files when debuging qmake projets | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | tal <talzarfati> |
Component: | CPP Debugger | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
tal
2003-10-28 14:05:10 UTC
Verified. This is what happens when I try to debug a "QMake project - Application" with every setting unchanged: (gdb) cd /home/jens/projects/delete_qmake_debuggertest/./bin (gdb) break delete_qmake_debuggertest.cpp:134 No source file named delete_qmake_debuggertest.cpp. It seems the debugger part assumes the source files are found in the same path as the executable, but the qmake templates sets it up so that the source is found in /home/jens/projects/delete_qmake_debuggertest/src/ I'm not sure if the problem is the debugger or the qmake project, but I suspect the former. remove the libtool in the project "options ...-> debugger" libtool isn't in there to begin with, so I doubt it's involved.. ;) Well, you have to compile your project with debug options, otherwise the debugger is missing the information, where to find the respective source files. The default config for a new qmake application is "release". If I switch to "debug" in the configuration of the src project and rebuild, the debugger finds the source files. If your project is properly configured as debug, and you still experience this problem, I need more information about your project settings to reproduce it. Otherwise I'm going to close this bug. Yup, you're right. (So sue me, I'd never used the qmake project before.. ;) ) Close away, it works fine. :) I think it worth considering to have "debug" be the default option for new projects though. There is rarely a reason to develop in release mode. closing this one as invalib because it isn't a bug. It's a user error :) |