Author Topic: Process terminated with status 127(0 minute(s), 0 second(s) in ubuntu  (Read 27078 times)

Offline gilbert

  • Single posting newcomer
  • *
  • Posts: 6
Hi m trying to create a simple hello world plugin in codeblocks but its not showing any output.. I am using codeblocks version 13.12 and OS ubuntu 12.04..

-------------- Build: default in test  (compiler: GNU GCC Compiler)---------------

g++ -I/usr/local/include/codeblocks -I/usr/local/include/codeblocks/tinyxml -I/usr/local/include/codeblocks/scripting/include -I/usr/local/include/codeblocks/scripting/bindings -I/usr/local/include/codeblocks/scripting/sqplus -I/usr/local/include/codeblocks/wxscintilla/include -I/usr/lib/i386-linux-gnu/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -pthread -ansi -fPIC -g -g -fPIC  -c "/home/sakina/Downloads/test/test /test.cpp" -o .objs/test.o
g++ -shared  .objs/test.o  -o libtest.so -L/usr/local/lib -lcodeblocks   -L/usr/lib/i386-linux-gnu -pthread -Wl,-Bsymbolic-functions -Wl,-z,relro  -L/usr/lib/i386-linux-gnu   -lwx_gtk2u_richtext-2.8 -lwx_gtk2u_aui-2.8 -lwx_gtk2u_xrc-2.8 -lwx_gtk2u_qa-2.8 -lwx_gtk2u_html-2.8 -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_xml-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8  -g 
Output file is libtest.so with size 155.44 KB
Running target post-build steps
zip -j9 test.zip manifest.xml
  adding: manifest.xml (deflated 53%)
zip -j9 test.cbplugin libtest.so test.zip
  adding: libtest.so
 (deflated 62%)
  adding: test.zip (deflated 13%)
Process terminated with status 0 (0 minute(s), 1 second(s))
0 error(s), 0 warning(s) (0 minute(s), 1 second(s))
 
-------------- Run: default in test  (compiler: GNU GCC Compiler)---------------

Checking for existence: /home/sakina/Downloads/test/test /libtest.so
Executing: codeblocks  (in /home/sakina/Downloads/test/test /.)
Process terminated with status 127 (0 minute(s), 0 second(s))


I even tried running the debugger it gives:


Building to ensure sources are up-to-date
Selecting target:
default
Adding source dir: /home/sakina/Downloads/test/test /
Adding source dir: /home/sakina/Downloads/test/test /
Adding file: codeblocks
Changing directory to: "/home/sakina/Downloads/test/test /."
Set variable: LD_LIBRARY_PATH=.:/usr/local/lib:/usr/lib/i386-linux-gnu:/usr/lib/i386-linux-gnu:

[debug]Command-line: /usr/bin/gdb -nx -fullname  -quiet  -args codeblocks
[debug]Working dir : /home/sakina/Downloads/test/test

Starting debugger: /usr/bin/gdb -nx -fullname  -quiet  -args codeblocks
done

[debug]Reading symbols from /usr/bin/codeblocks...(no debugging symbols found)...done.
[debug](gdb)
[debug]> set prompt >>>>>>cb_gdb:

Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints

[debug]>>>>>>cb_gdb:
[debug]> show version

Reading symbols from /usr/bin/codeblocks...(no debugging symbols found)...done.

[debug]GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
[debug]Copyright (C) 2012 Free Software Foundation, Inc.
[debug]License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[debug]This is free software: you are free to change and redistribute it.
[debug]There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
[debug]and "show warranty" for details.
[debug]This GDB was configured as "i686-linux-gnu".
[debug]For bug reporting instructions, please see:
[debug]<http://bugs.launchpad.net/gdb-linaro/>.
[debug]>>>>>>cb_gdb:
[debug]> set confirm off

Debugger name and version: GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04

[debug]>>>>>>cb_gdb:
[debug]> set width 0
[debug]>>>>>>cb_gdb:
[debug]> set height 0
[debug]>>>>>>cb_gdb:
[debug]> set breakpoint pending on
[debug]>>>>>>cb_gdb:
[debug]> set print asm-demangle on
[debug]>>>>>>cb_gdb:
[debug]> set unwindonsignal on
[debug]>>>>>>cb_gdb:
[debug]> set print elements 0
[debug]>>>>>>cb_gdb:
[debug]> set disassembly-flavor intel
[debug]>>>>>>cb_gdb:
[debug]> catch throw
[debug]Catchpoint 1 (throw)
[debug]>>>>>>cb_gdb:
[debug]> source /usr/local/share/codeblocks/scripts/stl-views-1.0.3.gdb
[debug]>>>>>>cb_gdb:
[debug]> directory "/home/sakina/Downloads/test/test /"
[debug]>>>>>>cb_gdb:
[debug]> run
[debug]/usr/bin/codeblocks: symbol lookup error: /usr/bin/codeblocks: undefined symbol: _ZN7Manager7isBatchE
[debug][Inferior 1 (process 4948) exited with code 0177]
[debug]>>>>>>cb_gdb:

[Inferior 1 (process 4948) exited with code 0177]

[debug]> quit

Debugger finished with status 0



pls Help..

Offline dmoore

  • Developer
  • Lives here!
  • *****
  • Posts: 1576
Re: Process terminated with status 127(0 minute(s), 0 second(s) in ubuntu
« Reply #1 on: March 30, 2014, 06:06:01 pm »
:D You can't easily "run" a plugin that's compiled against the globally installed C::B. When you click run it will switch to the already running instance. You can test your plugin in your running instance with Plugins -> Manage Plugins -> Install New... , select your cbplugin file, but this isn't really the recommended way to develop plugins because of the risk that it will crash C::B or screw up your settings.

If you want to debug your plugin, you will need to either check out and compile Code::Blocks from SVN then compile your plugin against it, or otherwise set the program arguments to run Code::Blocks with --multiple-instance, -ni and probably --user-data-dir (the latter will make sure your plugins don't corrupt your working user settings)


Offline stahta01

  • Lives here!
  • ****
  • Posts: 6609
    • My Best Post
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline dmoore

  • Developer
  • Lives here!
  • *****
  • Posts: 1576
Re: Process terminated with status 127(0 minute(s), 0 second(s) in ubuntu
« Reply #3 on: April 02, 2014, 05:30:31 pm »
Can u elaborate more on this.. plzz

Plugins -> Manager Plugins -> Install new... browse for your plugin and select it (and hope it doesn't crash Code::Blocks -- it won't if you've done everything right)

Otherwise build from source and compile and link your plugins against it -- read the link that Stahta provided. Unfortunately, our documentation for building plugins for Linux is a bit out of date.