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

List:       kdevelop-bugs
Subject:    [Bug 151175] New: GDB exited abnormally window when launching gdb
From:       ccalu <christian.chevalier () alcatel-lucent ! fr>
Date:       2007-10-22 10:25:03
Message-ID: 20071022122502.151175.christian.chevalier () alcatel-lucent ! fr
[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=151175         
           Summary: GDB exited abnormally window when launching gdb
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: christian.chevalier alcatel-lucent fr


Version:            (using KDE KDE 3.5.6)
Installed from:    I Don't Know
OS:                Linux

When I start gdb from Kdevelop, I get an error window : "GDB exited abnormally"
"This is likely a bug in GDB. Examine the gdb output window and then stop the debugger".

The gdb output window contains :
/bin/sh -c libtool gdb /home/cc/kscope --interpreter=mi2 -quiet
(gdb) Process exited

If I run this command in a shell, I get the following :
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require -mode=MODE be specified.
libtool: warning: cannot infer operation mode without MODE-ARGS
libtool: you must specify a MODE

But if I add quotes around the command and arguments :
/bin/sh -c "libtool gdb /home/cc/kscope --interpreter=mi2 -quiet"
gdb starts :
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require -mode=MODE be specified.
~"Using host libthread_db library \"/lib/tls/libthread_db.so.1\".\n"
(gdb)

So it doesn't seem to be a bug in GDB.
And I don't understand how the command /bin/sh -c can be run without quoting the following arguments.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]