05527: All sets: Debugger help text is missing words/lines

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
05527	Debugger	Minor	Always	Apr 16, 2014, 03:49	Apr 17, 2014, 13:56

Tester	AWJ	View Status	Public	Platform	SDLMAME
Assigned To		Resolution	Open	OS	Linux
Status [?]	Confirmed			Driver
Version	0.153	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	05527: All sets: Debugger help text is missing words/lines
Description	Type help (command name) and the help text will frequently be missing words or lines and/or with lines out of order. Changing the horizontal size of the debugger window can cause some of the missing words/lines to suddenly become visible (though not necessarily in the correct place), as can be seen by comparing the two attached screenshots.
Steps To Reproduce
Additional Information	Unlike the other recently reported debugger/cheat search bugs this isn't a 0.153 regression; I checked 0.152 and it already happens there. I haven't traced it back further than that.
Github Commit

Flags
Regression Version
Affected Sets / Systems	All sets

Attached Files	help1.png (128,688 bytes) Apr 16, 2014, 03:49 Uploaded by AWJ
Attached Files	help2.png (116,434 bytes) Apr 16, 2014, 03:50 Uploaded by AWJ

No.10575 AWJ Developer Apr 16, 2014, 03:56	Also notice the mysterious ", 57" next to the "help dasm" command. (I didn't type it, MAME added it)
No.10580 Tafoid Administrator Apr 16, 2014, 23:26 edited on: Apr 16, 2014, 23:30	Strange. That , 57 does not show automatically for me, but I can use it to adjust the text so that everything is in the window bounds. Using Windows (non-SDL), it is default and will make the text fit the window it makes so that no scrollbar on bottom is needed. My most recent SDL build (April 8th) shows the same thing happening where the ,57 is magically added to "help dasm" It's possible the side scrolling was never implemented when the SDL debugger was rewritten and the ,57 was the default used in testing?
No.10581 AWJ Developer Apr 16, 2014, 23:51	Tafoid, is there text missing in non-SDL Windows builds as well? The help text for the dasm command should read as follows: dasm dasm <filename>,<address>,<length>[,<opcodes>[,<cpu>]] The dasm command disassembles program memory to the file specified in the <filename> parameter. <address> indicates the address of the start of disassembly, and <length> indicates how much memory to disassemble. The range <address> through <address>+<length>-1 inclusive will be output to the file. By default, the raw opcode data is output with each line. The optional <opcodes> parameter can be used to enable (1) or disable(0) this feature. Finally, you can disassemble code from another CPU by specifying the <cpu> parameter.
No.10583 crazyc Developer Apr 17, 2014, 12:41 edited on: Apr 17, 2014, 12:42	With the regular win32 debugger, it doesn't happen. With the Qt debugger on windows, it does happen. (the ", 57" that is)
No.10584 Tafoid Administrator Apr 17, 2014, 13:56	AWJ: In Windows (non-SDL), the text can be off screen, but the window allows me to scroll to get to it. ON SDL/Qt, the side scroll option didn't appear when the window was resized and there was text beyond the window bounds.