I'm thinking about how one might do stack tracing so as to be useful in non-crash situations (Obviously a stack trace is not going to have calls that have been popped off, so if it's only recorded once during the process, it's useless) I know there are logging options for Twilight menu, but they probably don't detail code being run in dependencies. If this already exists, maybe you could ask users to enable stack tracing and upload the trace along with their bug report when applicable? It'd be worthwhile if you could enable stacktraces for twilight menu and nds-bootstrap. I suspect there are a lot of things deep in the dependencies that cause issues like these, but are cropping up now either due to poor documentation or assumptions made in the development of the deps. This isn't the first time there's been a known issue, with a known fix, that rob couldn't explain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |