[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 84251] New: gdb call cannot be configured
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2004-06-30 9:31:30
Message-ID: 20040630093130.21585.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=84251      
           Summary: gdb call cannot be configured
           Product: kdevelop
           Version: 3.0.4
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: robert.vogl esg de


Version:           3.0.4 (using KDE KDE 3.2.1KDE 1.2)
Installed from:    Compiled From SourcesCompiled From Sources
OS:                Linux

There is no possibility to configure the embedded call of the gdb. The only way to \
alter the initial gdb commands is to hack the source (gdbcontroller.cpp). I think \
this should be made configurable by a configuration file (e.g. if I would like gdb to \
ignore a SIGUSR1 signal.)

Also the command line arguments delivered by the internal gdb call are not \
configurable.

The gdb call should be more flexible.

It is desirable to enhance the already existing project specific configuration \
dialog.


[prev in list] [next in list] [prev in thread] [next in thread]