auto resize of output window makes this debugger unusable for my project

[mark4th]

I have created a curses library that allows for moveable, overlapping windows in a console. With this library I am developing an 8051 simulator that allows debuigging of 8051 code at both the assembler level (working) and at the C source level (soon).

However, I have a bug in the "div ab" opcode that has mysteriously come into existence and I need to track it down. I have used almost every single GDB interface and there is not one single one of them that is not pure, unadulterated GARBAGE. I absolutely loathe and despise every single one for being UTTERLY unusable.

I attempted to use your debugger which may very well (finally) be a good GDB interface but my application aborts on launch under your debugger due to a "window outside the bounds of the screen" error (my UI window in my UI screen in Your debuggers output window). This is happening because seer keeps resizing (or reinstantiating) the program output window on run.

If I drag the output window to be large enough for my console text user interface application to run in, the instant I do so my application CORRECTLY pukes on the console window being too small.

Can seer please not resie its application output window just because the user asked for a new run of an application?

[epasveer]

Thanks for trying Seer. I too loathe the debuggers out there. That's why I wrote my own :) Suggestions are very welcomed.

As to your issue. I've never been happy with my console. I'm looking for a better one but the ones I find are quite large. So, for the moment, I'm stuck with what I wrote.

Anyway, I think I can do something here. At least, for the immediate time, I can add a fixed size or at least a minimum size to the console. This, of course, will be a configuration setting.

So, even if the console window is shrunk, the actual size reported back is still the same.

Would this help?

[epasveer]

Actually, having thought about it, I think I'm reinstating the tty each time.

I can do something about that.

[mark4th]

I always set my X terminals to be 100 x 30 and this is a minimum for my own 8051 debugger because with anything smaller you just cant get all the information visible. If we could have a width/height config item for that output window that would be great :) p.s. see attached screenshot of the 8051 debugger. I also have a full UTF8 braille character set ray casting 3d engine in a console in my examples lol. slightly overboard maybe :) This is pretty much how I expect ALL debugers to look, disassembly or source in one window, registers and special function registers in another. A memory window and where i have the console window could also do double duty as a variable watch window. The way gdb -tui has multiple horizontal windows of the full width is HORRENDOUS lol. This debugger is still a major work in progress but I have "mostly (tm)" reverse engineered the Keil 8051 object module format (based on Intels omf51) that will allow me to do symbolic / source level debug soon. Im writing this because the processor im using at work literally has no debug what so ever beyond printf out the serial port :/ [image: 8051.png]

…

On Sat, Jan 4, 2025 at 6:57 PM Ernie Pasveer ***@***.***> wrote: Thanks for trying Seer. I too loathe the debuggers out there. That's why I wrote my own :) Suggestions are very welcomed. As to your issue. I've never been happy with my console. I'm looking for a better one but the ones I find are quite large. So, for the moment, I'm stuck with what I wrote. Anyway, I think I can do something here. At least, for the immediate time, I can add a fixed size or at least a minimum size to the console. This, of course, will be a configuration setting. So, even if the console window is shrunk, the actual size reported back is still the same. Would this help? — Reply to this email directly, view it on GitHub <#286 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6RP4EMCTDO33NIDKSMCHD2JBYOTAVCNFSM6AAAAABUTP7KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGQ2DGNRQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―

[epasveer]

p.s. see attached screenshot of the 8051 debugger.

I don't think the screenshot got attached properly. I don't see it.

[mark4th]

thats google for you, i could see it in the message before i clicked send lol. it is attached here again as a PNG

…

On Sun, Jan 5, 2025 at 5:08 AM Ernie Pasveer ***@***.***> wrote: p.s. see attached screenshot of the 8051 debugger. I don't think the screenshot got attached properly. I don't see it. — Reply to this email directly, view it on GitHub <#286 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6RP4EP6MG7DZDGGCP7IID2JEADLAVCNFSM6AAAAABUTP7KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRGU3TEMZTGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―

[epasveer]

Sorry, still haven't got the screenshot.

Perhaps send it directly to my email: [email protected]

Or, use cut-n-paste into this comment thread instead of attach.

[epasveer]

Added the screenshot to the thread for history sake. Your program looks good! Gotta love ncurses.

[mark4th]

actually thats my own curses library written from scratch, it allows moving, overlapping windows, full 24 bit RGB fg and bg or gray scales or normal palletised colors. The example code includes a Mandlebrot zoomer that uses the UTF8 braille character set and a 3d ray casting engine (like doom) also using the braille character set to draw the "graphics" with. github dot com slash mark4th slash uCurses. The only part of ncurses that I use is the terminfo database that comes with it. everything else was written by me. This is however how gdb -tui should look :/

…

On Sun, Jan 5, 2025 at 8:24 PM Ernie Pasveer ***@***.***> wrote: Added the screenshot to the thread for history sake. Your program looks good! Gotta love ncurses. image.png (view on web) <https://github.com/user-attachments/assets/b823e6da-7f10-43bb-b6bf-63fb608df45d> — Reply to this email directly, view it on GitHub <#286 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6RP4BW7PWJKQ3DB5I4H5T2JHLN5AVCNFSM6AAAAABUTP7KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRHA2DOOBTGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―

[mark4th]

oh it is not quite as good as ncurses because there are some glitches that I get in certain terminals that I have not figured out how to fix :/

…

On Sun, Jan 5, 2025 at 8:39 PM Mark Manning ***@***.***> wrote: actually thats my own curses library written from scratch, it allows moving, overlapping windows, full 24 bit RGB fg and bg or gray scales or normal palletised colors. The example code includes a Mandlebrot zoomer that uses the UTF8 braille character set and a 3d ray casting engine (like doom) also using the braille character set to draw the "graphics" with. github dot com slash mark4th slash uCurses. The only part of ncurses that I use is the terminfo database that comes with it. everything else was written by me. This is however how gdb -tui should look :/ On Sun, Jan 5, 2025 at 8:24 PM Ernie Pasveer ***@***.***> wrote: > Added the screenshot to the thread for history sake. Your program looks > good! Gotta love ncurses. > > image.png (view on web) > <https://github.com/user-attachments/assets/b823e6da-7f10-43bb-b6bf-63fb608df45d> > > — > Reply to this email directly, view it on GitHub > <#286 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE6RP4BW7PWJKQ3DB5I4H5T2JHLN5AVCNFSM6AAAAABUTP7KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZRHA2DOOBTGA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―

-- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―

[epasveer]

actually thats my own curses library written from scratch,

That's so cool.

I'm hopeful I can use your demo example to reproduce the bug you're encountering with Seer.

[mark4th]

you should be able to, i think it also requires a 100x30 terminal to run most of the demos in there. as stated, uCurses does not always behave sanely in all terminals, i have not fully figured this out but i have not been looking that hard for it, very busy with work lol uCurses is known to run just fine in a gnome terminal and with konsole.

…

On Mon, Jan 6, 2025 at 9:54 AM Ernie Pasveer ***@***.***> wrote: actually thats my own curses library written from scratch, That's so cool. I'm hopeful I can use your demo example to reproduce the bug you're encountering with Seer. — Reply to this email directly, view it on GitHub <#286 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE6RP4C5KJVFG2L62PWAJR32JKKJLAVCNFSM6AAAAABUTP7KRCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGI3TOMZSGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- “When something can be read without effort, great effort has gone into its writing.” ― Enrique Jardiel Poncela ―