Pages: 1
  Print  
Author Topic: Incorrect display of g++ messages on Progress window  (Read 2341 times)
Offline (Unknown gender) tiborbuzasi
Posted on: August 15, 2019, 01:58:22 AM
Member
Joined: Sep 2014
Posts: 2

View Profile
I've been running into the same 'issue' both on Windows 7 x64 and Kubuntu 19.04 x64 (building enigma-dev from the source this morning and yesterday evening, respectively):
The error message of g++ is full of strange characters (see the attached image), which makes debugging even harder.

EDIT: providing some more info:
« Last Edit: August 15, 2019, 02:48:47 PM by tiborbuzasi » Logged
Offline (Male) time-killer-games
Reply #1 Posted on: August 15, 2019, 05:14:44 AM

Contributor
Location: Virginia Beach
Joined: Jan 2013
Posts: 1157

View Profile Email
Yeah, normally it's a lot easier for me to debug errors like this with my own projects, simply because it's apparent enough what the exact code it is referencing is. I don't have access to your code, so it makes it that much more difficult for me to understand, I would recommend joining our discord and getting help from Josh there, or posting this as an issue on GitHub if there isn't already one posted for this.
Logged
Offline (Unknown gender) tiborbuzasi
Reply #2 Posted on: August 15, 2019, 02:48:03 PM
Member
Joined: Sep 2014
Posts: 2

View Profile
Sorry, if the point of this issue was not clear: I'm asking why the output of g++ is littered if the characters (like ) in the g++ output have any special meaning or is there a known way to make them disappear to make the log more readable. This issue seems not to be related with my project as I tried to compile various source files from EDC and the g++ output appeared in the same style.

PS: added some more info to the first entry.
Logged
Offline (Male) time-killer-games
Reply #3 Posted on: August 15, 2019, 03:26:09 PM

Contributor
Location: Virginia Beach
Joined: Jan 2013
Posts: 1157

View Profile Email
What i was trying to say is this is an obvious bug, and someone should report it if it hasn't been already. No, there is no way to 'turn it off', and no, it has no direct meaning. It needs to be fixed by one of the developers, most likely Josh. I only work on the engine, and don't know anything about how the compiler works. If it bothers you enough, make a GitHub ticket.
Logged
Offline (Male) hpg678
Reply #4 Posted on: August 16, 2019, 08:56:15 AM

Member
Location: Barbados
Joined: Mar 2017
Posts: 261

View Profile Email
Greetings!


Unfortunately, I do get those as well.


There is a script at the root of 'enigma-dev' directory named "share_logs.sh" that will solve this........if you mind doing the extra work. As i understand it, you run the script in a terminal/shell window and it will strip those extra characters and create a pastebin file for you.


You can also use 'gdb' to debug your errors. Run the game in debug mode. Copy the name of resulting file....for example "/tmp/emg23453464548765342768.tmp" if you are running Linux;............. "C:/msys32/tmp/egm8652499151924152154.exe"...if you running Windows.
Open a Terminal window. (on windows open a Msys Shell Terminal, not a Powershell)
At the prompt, type gdb[ name of file you copied].
then type  'run'.


There you have it. You can use either of the two methods to debug your game. I personally have opted for the tedious method of looking through the output and figuring out where i made an error. This is only because i am meticulously saving the slightest change, so it is easier for me to know where i went wrong. :) :)


Hope this has 'helped' you out a bit. You can find on the discord channel. Or if you prefer, contact me here for anything else.


 (Y) (Y)

Logged
Hugar
Pages: 1
  Print