https://github.com/TylerGlaiel/Crashlogs Skip to content Toggle navigation Sign up * Product + Actions Automate any workflow + Packages Host and manage packages + Security Find and fix vulnerabilities + Codespaces Instant dev environments + Copilot Write better code with AI + Code review Manage code changes + Issues Plan and track work + Discussions Collaborate outside of code Explore + All features + Documentation + GitHub Skills + Blog * Solutions For + Enterprise + Teams + Startups + Education By Solution + CI/CD & Automation + DevOps + DevSecOps Case Studies + Customer Stories + Resources * Open Source + GitHub Sponsors Fund open source developers + The ReadME Project GitHub community articles Repositories + Topics + Trending + Collections * Pricing [ ] * # In this repository All GitHub | Jump to | * No suggested jump to results * # In this repository All GitHub | Jump to | * # In this user All GitHub | Jump to | * # In this repository All GitHub | Jump to | Sign in Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. {{ message }} TylerGlaiel / Crashlogs Public * Notifications * Fork 0 * Star 36 A simple way to output stack traces when a program crashes in C++, using the new C++23 header License MIT license 36 stars 0 forks Star Notifications * Code * Issues 0 * Pull requests 0 * Actions * Projects 0 * Security * Insights More * Code * Issues * Pull requests * Actions * Projects * Security * Insights TylerGlaiel/Crashlogs This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. main Switch branches/tags [ ] Branches Tags Could not load branches Nothing to show {{ refName }} default View all branches Could not load tags Nothing to show {{ refName }} default View all tags Name already in use A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch? Cancel Create 1 branch 0 tags Code * Local * Codespaces * Clone HTTPS GitHub CLI [https://github.com/T] Use Git or checkout with SVN using the web URL. [gh repo clone TylerG] Work fast with our official CLI. Learn more about the CLI. * Open with GitHub Desktop * Download ZIP Sign In Required Please sign in to use Codespaces. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching GitHub Desktop If nothing happens, download GitHub Desktop and try again. Launching Xcode If nothing happens, download Xcode and try again. Launching Visual Studio Code Your codespace will open once ready. There was a problem preparing your codespace, please try again. Latest commit @TylerGlaiel TylerGlaiel Update crashlogs.cpp ... d3d1f40 Jul 3, 2023 Update crashlogs.cpp removed cout statements I forgot to remove d3d1f40 Git stats * 5 commits Files Permalink Failed to load latest commit information. Type Name Latest commit message Commit time LICENSE Initial commit July 2, 2023 15:59 README.md Update README.md July 2, 2023 16:18 crashlogs.cpp Update crashlogs.cpp July 3, 2023 13:05 crashlogs.h Add files via upload July 2, 2023 15:59 View code README.md Crashlogs A simple way to output stack traces when a program crashes in C++, using the new C++23 header currently windows-only, but if anyone wants to add mac or linux support I'll merge it in usage: include the files in your project, then call glaiel::crashlogs::begin_monitoring(); to enable crash handling (probably do this at the start of your program) when the program crashes, it will save a timestamped stack trace to the folder specified with glaiel::crashlogs::set_crashlog_folder(folder_path); some additional customizability and callbacks are documented in the header file note: the stack trace outputted will include a bunch of error handling stuff at the top. It would be nice to skip printing the first X stack trace entries, but how many to skip seems kinda dependent on optimization settings and which condition triggered the error handler, so I did not bother with that yet. About A simple way to output stack traces when a program crashes in C++, using the new C++23 header Resources Readme License MIT license Stars 36 stars Watchers 1 watching Forks 0 forks Report repository Releases No releases published Packages 0 No packages published Languages * C++ 100.0% Footer (c) 2023 GitHub, Inc. Footer navigation * Terms * Privacy * Security * Status * Docs * Contact GitHub * Pricing * API * Training * Blog * About You can't perform that action at this time.