cl-trivial-backtrace 20200511.git6eb65bd-1 source package in Ubuntu
Changelog
cl-trivial-backtrace (20200511.git6eb65bd-1) unstable; urgency=medium [ Sébastien Villemot ] * New upstream snapshot * Mark autopkgtests as superficial * Bump to debhelper 13 * Bump S-V to 4.5.1 [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.5.0, no changes needed. -- Sébastien Villemot <email address hidden> Mon, 07 Dec 2020 14:06:10 +0100
Upload details
- Uploaded by:
- Debian Common Lisp Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Common Lisp Team
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
cl-trivial-backtrace_20200511.git6eb65bd-1.dsc | 2.2 KiB | 37206f15fd1e013e63bf9b6e69a7aa7539052c8ddcfd7c9a9d4b841410768441 |
cl-trivial-backtrace_20200511.git6eb65bd.orig.tar.xz | 8.6 KiB | 75ba7d6a1beda5162e15c8780d9a7e58ddbcd935c00e5119b490d9f79322837f |
cl-trivial-backtrace_20200511.git6eb65bd-1.debian.tar.xz | 3.0 KiB | 90599a5f38d1d072ae07c8fc12d5a4a39909aed943ae385f0c4cafa41b2ac114 |
Available diffs
No changes file available.
Binary packages built by this source
- cl-trivial-backtrace: generate a Common Lisp backtrace portably
One of the many things that didn't quite get into the Common Lisp standard
was how to get a Lisp to output its call stack when something has gone
wrong. As such, each Lisp has developed its own notion of what to display,
how to display it, and what sort of arguments can be used to customize it.
trivial-backtrace is a simple solution to generating a backtrace portably.
.
It supports Allegro Common Lisp, LispWorks, ECL, MCL, SCL, SBCL and CMUCL.