User forums > Help

Debugging problem in a console application with ncurses library

<< < (2/3) > >>

Freem:
The versionning system of Code::Blocks is the same as Ubuntu's one:
The first number is the 2 last digits of the year, the  last one is the month's number.

All of this mean that you use a version of May 2010.
The post before you with the bug corrected is dated from July 20, 2010.

Try to use a nightly build, this problem is probably resolved there.
They are quite stable, and supported.

Look there: http://forums.codeblocks.org/index.php/topic,15023.0.html

tjareson:
Hello,

has anybody tried, if this problem is solved in a version > 10.05 ?

I'm using 10.05 and have the same problem. Workaround helps, but the problem is more the time it takes until one gets the idea that the debugging itself causes this problem.
(drove me nuts for almost an hour...)


Cheers
Tjareson

Krice:
This is a bit old topic, but still seems to be valid, because I have the same problem in Fedora. Changing terminal doesn't seem to fix it, same problem with gnome's default or xterm which I'm using for this project. Code::Blocks shows this error:


--- Code: ---Set variable: LD_LIBRARY_PATH=.:
Starting debugger: /usr/bin/gdb -nx -fullname -quiet  -args /home/krice/projects/saladir/bin/Debug/saladir
Setting SHELL to '/bin/sh'
done
Setting breakpoints
Debugger name and version: GNU gdb (Fedora Linux) 16.3-1.fc42
Error opening terminal: unknown.
[Inferior 1 (process 7216) exited with code 01]
Debugger finished with status 0

--- End code ---

I've tried to find answers to this, but looks like no one has solved this in... about 20 years? ps. Running in normal mode works, only debugging fails.

Bug Killer:
What is the value of the environment variable TERM of the terminal session ?

Krice:

--- Quote from: Bug Killer on June 18, 2025, 03:02:51 pm ---What is the value of the environment variable TERM of the terminal session ?
--- End quote ---

How do you check that? By the way, the problem seems to be curses, if I try a SDL2 project then debugging works. I think I read somewhere that when debugging curses programs people have to run two terminal instances, one for curses and another for gdb, but that is on command line.

Navigation

[0] Message Index

[#] Next page

[*] Previous page