Bug 60990 - The setting of tty in the gdb subprocess should be changeable
Summary: The setting of tty in the gdb subprocess should be changeable
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 4.0.0
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-09 15:34 UTC by Sven Fischer
Modified: 2008-06-29 18:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Fischer 2003-07-09 15:34:22 UTC 
Version:           Gideon (CVS) (using KDE KDE 3.1.2)
Installed from:    Debian testing/unstable Packages
OS:          Linux

I am using a script to remotely start a gdb process. If the tty wouldn't be changed, the debugging process would work fine. But since the tty kdevelop uses isn't available remotely, the start of the application to be debugged fails.

So, make the execution of the tty command configurable.

Or, even better, make all commands customizable via text files with placeholders, so other debuggers could be integrated into gideon.
Comment 1 Vladimir Prus 2005-08-19 11:16:14 UTC 
So, you're running *gdb* remotely. Is there a reason why you can't run gdb locally, and invoke gdbserver remotely? I'm not saying that KDevelop hardcoded tty setting is OK, just want to better understand your use case.
Comment 2 Sven Fischer 2005-08-19 15:09:34 UTC 
The reason is, the remote OS is QNX, which does not have a gdbserver. It has it's own remote debugging toolset for cross-platform development, which is not compatible with a Linux gdb.
Comment 3 Andreas Pakulat 2008-06-29 18:44:29 UTC 
*** Bug has been marked as fixed ***.