FS#45714 - [terminology] Stack smashing detector kills terminology after KB input

Attached to Project: Community Packages
Opened by Hermann Zahnweh (eigengrau) - Sunday, 19 July 2015, 16:06 GMT
Last edited by Carsten Haitzler (raster) - Wednesday, 16 June 2021, 08:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ronald van Haren (pressh)
Carsten Haitzler (raster)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
terminology runs fine as long as the interaction with the window is restricted to mouse input. When the first keyboard input is made, the stack smashing detector kills the process. Build issue or upstream?

Additional info:
* terminology 0.8.0-1

Steps to reproduce:
Launch terminology, issue keyboard input.
This task depends upon

Closed by  Carsten Haitzler (raster)
Wednesday, 16 June 2021, 08:23 GMT
Reason for closing:  Not a bug
Additional comments about closing:  probably well obsolete by now after 6 years...
Comment by Hermann Zahnweh (eigengrau) - Sunday, 19 July 2015, 16:07 GMT
stdout after termination.
   stdout (42.4 KiB)
Comment by Ronald van Haren (pressh) - Tuesday, 21 July 2015, 15:17 GMT
Sorry, I can't replicate it on x86_64, anything special I should do besides typing in the window?
Comment by Hermann Zahnweh (eigengrau) - Thursday, 23 July 2015, 09:52 GMT
I prodded around a bit and have noticed that the SSP kicking in depends on the setting of the ECORE_IMF_MODULE variable. I need xim as my input method there, and this triggers the kill.

Try and see if exporting «ECORE_IMF_MODULE=xim» before running terminology triggers the SSP for you.
Comment by Carsten Haitzler (raster) - Wednesday, 16 June 2021, 08:23 GMT
this is probably well obsolete by now. i've run terminology with asan on and not seen anything... not in the past few years. so .. time to kill as this is well obsolete. please report upstream if you have issues... :)

Loading...