Skip to content

check _console_buffer against current console destbuffer - #270

Open
Naim2000 wants to merge 1 commit into
devkitPro:masterfrom
Naim2000:patch-2
Open

check _console_buffer against current console destbuffer#270
Naim2000 wants to merge 1 commit into
devkitPro:masterfrom
Naim2000:patch-2

Conversation

@Naim2000

Copy link
Copy Markdown
Contributor

Fixes the issue where using normal CON_Init after using CON_InitEx makes the system continue printing on the Ex buffer. which is a weird use case, but is effectively what happens when the exception handler is called

(warning: this is a kind of bandaid fix, because I am not trying to refactor the other half of console in a single pr)

@DacoTaco

Copy link
Copy Markdown
Member

imo a better fix would be for __console_init to free/null the buffer when its called.

what do you think @fincs ?

@fincs

fincs commented Aug 27, 2026

Copy link
Copy Markdown
Member

Note that the exception dump screen happens from within exception context, and therefore it is not allowed to call malloc/free. I'd suggest simply setting the pointer to null.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants