peoplesome have exploited this problem when they were unable to debug kdevelop on their own. The problem occurs every time the debug wrapper is libtool and then autotools build creates the libtool wrapper system scripts to ensure the application starts.
To play, create any kde package from a template, add a subproject, add a working libtool with the library installed and build it. You will see that $ (top_builddir) / src / appname is no longer a great executable, but rather a wrapper around libtool . The same applies to the Kdevelop source tree.
But my debugger seems to be trying to define the script as executable. : -s_waitForWrite kdevelop (Debugger): ANSWER: & “File / home / gremlin / projects / tests / tk334 / debug / src / tk334 n” kdevelop (Debugger): COMMANDS: 1 in one line, 1 Execute kdevelop (Debugger): ANSWER: & “” / home / gremlin / projects / tests / tk334 / debug / src / tk334 “: not when it comes to executable Format: unrecognized file format n “
This is because KDevelop launches the debugger withI use the following command: / bin / sh -c / home / gremlin / projects / tests / tk334 / debug / libtool gdb –interpreter = mi2 – quiet instead of libtool gdb –interpreter = mi2 -quiet src / tk334
Note the path to the libtool shell script throughout the command line. Vladimir, could you strategy. what’s the plan who?
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
Post by Alexander Daimo Many would like people to see this problem when they couldn’t debug kdevelop on their own. The problem occurs when the debug wrapper is always libtool and the autotools build system builds libtool wrapper software packages to run the application. To reproduce, you build many kde applications from a template, add a > subproject, put in the libtool installed in lib, and build accordingly. You will see that $ (top_builddir) / src / appname is far from an executable file, but rather a libtool wrapper script. It’s the same with the Kdevelop source tree.
Hello Alexander! You can describe the breeding steps in more detail or, better yet, send a small reconstruction where this problem occurs. I did my best thatwould follow the steps above and finally got “No to build rules XXX.la.lo”. Perhaps this is still due to the fact that I never liked Automake.
Courtesy of Vladimir Prus Buyers can provide more details on the stages of reproduction, or better yet, submit a small project that causes this problem. I tried the steps above and got the message “There is no rule to create XXX.la.lo”. Maybe this is different from the fact that I’ve never used Automake.
You will probably try: http://www.ki-inform.com/~adymo/code/tk334.tar.bz2 Just create it with you to see the debug / src wrapper / tk334 script.
Hello Alexander, thanks for the test case; in general, the error is reproduced by me (after optimizing the configuration parameters do not use 64-bit libraries 😉
I’ll take some time to consider if this is really the best way, and hopefully will fix it by the end of the week.
Post by Vladimir Prus you can study the stages of reproduction in more detail, or even better – send a small project in which this problem occurs. I tried to follow the given steps and got the message “There is no rule to create XXX.la.lo”. Perhaps this is due to the fact that I have never used Automake.
http://www.ki-inform.com/~adymo/code/tk334.tar.bz2 Just create owners and see the debug / src / tk334 shell script.
Fixed, now it turns out that the “end of the week” is a little ambiguous.
I don’t know what to do with this. Alternatively, we must first extract the exact component from the supplied command, as well as the fact that it exists No, or we have to add –mode = run ourselves, in the case of the “Debug shell” protection cannot be completely except for libtool.
Hello, Alexander! Thanks for the test case; the error repeats only for me (after setting parameters, which do not necessarily use 64-bit libraries 😉 I will take time to think what is the best way to fix this problem, and hopefully everything will be fixed to the end weeks.
A message about Vladimir Prus can you describe the found reproduction in more detail, step by step or even better, send a real small project that has this problem. I tried to follow steps and above: “There is no rule for creating XXX.la.lo”. It is possible that I have never used an auto site.
http://www.ki-inform.com/~adymo/code/tk334.tar.bz2 Just compile it and see the debug / src / tk334 shell script.
