| Summary: | Debugging with GDB in shell | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Erik <eriksq> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | crash | CC: | Ekkehard.Blanz, kfunk, vlas.puhov |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 4.5.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Erik
2014-01-14 16:06:21 UTC
I did some research before posting this bug. Similar unresolved issues have been appearing since 2009: http://www.qtcentre.org/archive/index.php/t-8444.html If this is not really a bug but a usage problem, maye the debug setup page needs better examples, or automatic fix buttons? In any case, KDevelop shouldn't crash. We'll have a look at it. Hey Kevin, Thank you for not making me state the obvious. :) Let me know, Erik On 01/14/2014 11:14 AM, Kevin Funk wrote: > https://bugs.kde.org/show_bug.cgi?id=329960 > > Kevin Funk <kevin@kfunk.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kevin@kfunk.org, > | |vlas.puhov@mail.ru > > --- Comment #2 from Kevin Funk <kevin@kfunk.org> --- > In any case, KDevelop shouldn't crash. We'll have a look at it. > Apparently Vlas added support for that in KDevelop 4.6. Author: Vlas Puhov <vlas.puhov@mail.ru> Date: Tue Oct 22 23:33:07 2013 +0400 Make it possible to debug from external terminals. Currently supported: konsole, xterm, gnome-terminal and xfce4-terminal. BUG: 204638 But somehow, that even doesn't work for me. If I set the debugging shell to /usr/bin/konsole, KDevelop just switches to the Debug area, and then immediately switches back to the code view. Vlas, can you check if that's working as intended? >Apparently Vlas added support for that in KDevelop 4.6. >But somehow, that even doesn't work for me. Actually it shouldn't. I have no idea what purpose of "Debugging shell" option... To debug from external terminals (e.g. konsole ) use "External terminal" option. >If I set the debugging shell to /usr/bin/konsole, KDevelop just switches to the Debug area, and then immediately switches back to the code view. Yes, it does the same for me. So, Erik, I guess you should use a more recent version of kdevelop e.g. 4.6 or git master http://techbase.kde.org/Projects/KDevelop4/HowToCompile Also, Kevin, what do you think about removing "Debugging shell" option? I find this option very confusing, and it's purpose is not very clear for me. Uh oh. I confused the "External terminal" and "Debugger Shell" option. So, yeah, given this, I don't know what the purpose of "Debugger Shell" is either. The tooltip hint says something about automake projects, but I'm clueless why overwriting the shell in use would help anything. Code is from Roberto from 2004, so dead-old, and has been dragged along through multiple refactorings. So I'm also wondering if it's *still* useful... Maybe worth asking the kdevelop mailing list. I am trying to compile the latest Kdevelop, but am running into an
undocumented requirement/issue.
CMake Error: The following variables are used in this project, but they
are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
QT_QT_INCLUDE_DIR
used as include directory in directory
/home/erik/src/kdevplatform/build/CMakeFiles/CMakeTmp
A little hint here? I've installed libqt4-dev, -core, and -gui
What's missing? The compile docs don't mention this variable setting
being required.
On 01/15/2014 04:00 AM, Vlas Puhov wrote:
> https://bugs.kde.org/show_bug.cgi?id=329960
>
> Vlas Puhov <vlas.puhov@mail.ru> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|CONFIRMED |RESOLVED
> Resolution|--- |INVALID
>
> --- Comment #5 from Vlas Puhov <vlas.puhov@mail.ru> ---
>> Apparently Vlas added support for that in KDevelop 4.6.
>> But somehow, that even doesn't work for me.
> Actually it shouldn't. I have no idea what purpose of "Debugging shell"
> option...
> To debug from external terminals (e.g. konsole ) use "External terminal"
> option.
> >If I set the debugging shell to /usr/bin/konsole, KDevelop just switches to
> the Debug area, and then immediately switches back to the code view.
> Yes, it does the same for me.
>
> So, Erik, I guess you should use a more recent version of kdevelop e.g. 4.6
> or git master http://techbase.kde.org/Projects/KDevelop4/HowToCompile
>
> Also, Kevin, what do you think about removing "Debugging shell" option? I
> find this option very confusing, and it's purpose is not very clear for me.
>
Eric, this is offtopic to this bug. Please post these kind of questions to the mailing list, or just join #kdevelop on Freenode. Hint: You're probably running into something like: http://ubuntuforums.org/showthread.php?t=2168435 (Qt4 vs. Qt5 collision issue) Just finished compiling. I now get " Can't receive /usr/bin/konsole tty/pty. Check that /usr/bin/konsole and that it accepts these arguments...." and then crashes. This happens no matter what I put into the debug shell entry, be it konsole or /bin/bash Git commit d6ebd12d2ab2554d4e16c1df88c20d647abe3260 by Vlas Puhov. Committed on 16/01/2014 at 17:11. Pushed by vpuhov into branch 'master'. Turn "whats this" messages into tooltip messages. Obviously no one reads "whats this" messages, so let's show it as tooltips, they are not so long after all. Also clarify some messages. M +40 -44 debuggers/gdb/debuggerconfigwidget.ui http://commits.kde.org/kdevelop/d6ebd12d2ab2554d4e16c1df88c20d647abe3260 >This happens no matter what I put into the debug shell entry, be it konsole or /bin/bash You shouldn't put anything into "debug shell" entry. (see the last commit). >Just finished compiling. I now get " Can't receive /usr/bin/konsole tty/pty. Check that /usr/bin/konsole and that it accepts these arguments...." and then crashes. Attach the backtrace then. I guess it should be different from the one that is already here. Created attachment 85094 [details]
New crash information added by DrKonqi
kdevelop (4.5.1) on KDE Platform 4.11.5 using Qt 4.8.4
Tried to use an external terminal for a debug session. Crashed in the attempt to do so.
-- Backtrace (Reduced):
#6 0x00007f7d716fba9e in GDBDebugger::DebugSession::startProgram (this=0xba97160, cfg=0xbaf2c70) at ../../../debuggers/gdb/debugsession.cpp:1023
#7 0x00007f7d71703de7 in GDBDebugger::DebugJob::start (this=0xbe80c90) at ../../../debuggers/gdb/debugjob.cpp:104
#8 0x00007f7d9575fb4c in KDevelop::RunController::registerJob (this=0x24808c0, job=0xb650d40) at ../../shell/runcontroller.cpp:575
#9 0x00007f7d957619cb in KDevelop::RunController::execute (this=this@entry=0x24808c0, runMode=..., launch=<optimized out>) at ../../shell/runcontroller.cpp:405
#10 0x00007f7d95762870 in KDevelop::RunController::executeDefaultLaunch (this=this@entry=0x24808c0, runMode=...) at ../../shell/runcontroller.cpp:822
|