Lazarus

Using the Lazarus IDE => General => Topic started by: huckfinn on October 22, 2019, 06:18:58 pm

Title: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: huckfinn on October 22, 2019, 06:18:58 pm
Hi, I've installed Lazarus 2.0.4 under FreeBSD 12 using the ports collection.  Unfortunately I cannot find the Item 'Terminal Output' in the  in Menu 'View' -> 'Debug Windows' for an simple console application. Is there a possibility to bring that window on screen.  Best Regards Huck
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: Handoko on October 22, 2019, 06:26:57 pm
Hello huckfinn,
Welcome to the forum.

Have you try:
Lazarus main menu > View > Debug Windows > Console In/Output

Maybe you need:
Lazarus main menu > Window > Center a lost window > Console In/Output
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: huckfinn on October 22, 2019, 06:47:03 pm
Hi Handoko, yes I've tried to find the 'Console Item' at both places of the GUI, but cant see them. On my Linux PC (Debian 8 & Lazarus 1.6.2) it resides directly below 'View -> Debug Windows -> Local Variables' entry for example. I also think, that the 'Center a lost window' feature, works only for open windows. Is it possible, that this feature is not supported by FreeBSD implementation?
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: Handoko on October 22, 2019, 06:54:25 pm
As far as I know Lazarus has some issues running on FreeBSD.
https://wiki.lazarus.freepascal.org/FreeBSD

I think the missing Terminal Output on FreeBSD is an unimplemented feature or maybe a bug. You can check the bug tracker if it hasn't reported you maybe want to submit a bug report:
http://bugs.freepascal.org/set_project.php?project_id=6
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: huckfinn on October 22, 2019, 07:29:12 pm
I've reported the behaviour under the issue 36203: https://bugs.freepascal.org/view.php?id=36203. Best regards Huck
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: Martin_fr on October 22, 2019, 07:53:34 pm
probably a missing $IFDEF

Assuming that the code for a virtual tty is the same as on Linux.

It may need special code though....
Same on OSX, No one has found out how the IDE can create a tty.
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: huckfinn on October 22, 2019, 11:30:04 pm
Thank you Martin, do have you a workaround beyond the strategy of transforming 'console test routines'  into GUI applications to get visual debugging capabilities under FreeBSD. Or is it better to stay on a Linux based device for that matter. Best regards Huck
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: Martin_fr on October 23, 2019, 12:47:58 pm
As I said find the ifdef s. and test....

I am away. I may be able to point to the ifdef next week. but I do not have a fbsd setup to test.

crude workarounds https://wiki.lazarus.freepascal.org/Debugger_Console_App
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: Martin_fr on October 26, 2019, 02:22:16 am
Ok, try compiling the IDE and packages (Tools > configure build lazarus) with
-dDBG_ENABLE_TERMINAL

As I said, I don't have a bsd setup, so I haven't tested if it will work.
Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: huckfinn on November 19, 2019, 06:59:21 pm
I've tried to enable the terminal, but ended up with an:

lazarus.pp(165,1) Error: Error while linking

without any trace of compiler error.

Code: [Select]
LCL widget type: GTK2
Target OS: FReeBDS
Target CPU: x86_64
-d DBG_ENABLE_TERMINAL


Title: Re: Missing the Terminal Output Item in Menu View / Debug Windows
Post by: MarkMLl on November 19, 2019, 08:19:37 pm
Assuming that you're compiling/linking from a shell session (i.e. rather than getting the IDE to rebuild itself) work back through the error messages and you'll find an indication of what's missing. I was looking at that code under Linux a few months ago adding various output representations and I'm pretty sure I saw something similar happening.

MarkMLl