{"id":281,"date":"2009-04-25T01:36:39","date_gmt":"2009-04-25T06:36:39","guid":{"rendered":"http:\/\/www.visophyte.org\/blog\/?p=281"},"modified":"2009-04-25T01:36:39","modified_gmt":"2009-04-25T06:36:39","slug":"gaudily-syntax-highlighted-code-listings-in-archer-gdb","status":"publish","type":"post","link":"https:\/\/www.visophyte.org\/blog\/2009\/04\/25\/gaudily-syntax-highlighted-code-listings-in-archer-gdb\/","title":{"rendered":"gaudily syntax-highlighted code listings in (archer) gdb"},"content":{"rendered":"

\"pyglist<\/a><\/p>\n

Gaudily syntax-highlighted code listing in gdb joins the gaudy gdb plugin family!\u00a0 (Other members include gaudily colorized backtraces<\/a>, which you can also see in the bottom of the screenshot.)\u00a0 This, of course, requires gdb with python crammed inside<\/a>.\u00a0 It might require one crammed a few months ago too; I haven’t updated my archer-gdb repo for at least that long.<\/p>\n

The “sl” plugin uses Pygments<\/a> for the syntax highlighting.\u00a0 Although pygments has a 256 color terminal formatter (woo!), I ended up using my pyflam module because it did not support my need to color the background of the current line without doing something convoluted.\u00a0 (I would have had to create a filter that did its own line-counting and created background-color-styled token variant of every token on the desired line.)\u00a0 Also, it didn’t do line numbers.<\/p>\n

The color theme is based off the “fruity” color theme.\u00a0 Much of the gaudy comes from a filter I added that tries to do various Mozilla C++-aware code styling things by recognizing naming patterns of Name tokens.\u00a0 Before you complain about the colors hurting your brain, remember that this is the alternative:<\/p>\n

\"not-pyglist,<\/a><\/p>\n

That’s right.\u00a0 It’s like looking at static.\u00a0 You can barely make anything out.\u00a0 And imagine if it was more than just the 10 lines “list” gives you.<\/p>\n

Anywho, the repo is here: http:\/\/hg.mozilla.org\/users\/bugmail_asutherland.org\/pythongdb-gaudy\/<\/a><\/p>\n

The README tells you what to do.\u00a0 For complete-ness, and because I went to all the effort to write documentation for the command, here is what it does!<\/p>\n

Prints a syntax-highlighted source listing.  Currently limited to only\r\nwork based on the current debug frame and position.\r\n\r\nBy default, the 11 lines before the current position and 8 lines after are\r\ndisplayed.  A line context is saved between command invocations if the current\r\nsource line does not change.\r\n\r\nArguments when used in a new context:\r\n  (none)  Shows the 11 lines before the current position and 8 lines after.\r\n  N       Shows the N\/2 lines befores the current position and N\/2 lines after.\r\n  -N      Shows the N lines before the current position and 8 lines after.\r\n  +N      Shows the 11 lines before the current position and N lines after.\r\n  M N     Shows the M lines before the current position and N lines after.\r\n\r\nArguments in an existing context:\r\n  (none)  Shows the 20 lines after the last-shown lines.\r\n  -       Shows the 20 lines preceding the last-shown lines.\r\n  N       Shows the N lines after the last-shown lines.\r\n  -N      Shows the N lines preceding the last-shown lines.\r\n  M N     Shows the M last lines of the last-shown lines and N lines after the\r\n            last-shown lines.\r\n\r\nArguments regardless of context\r\n  @A,B    Shows lines A through B.<\/pre>\n","protected":false},"excerpt":{"rendered":"
Gaudily syntax-highlighted code listing in gdb joins the gaudy gdb plugin family!\u00a0 (Other members include gaudily colorized backtraces, which you can also see in the bottom of the screenshot.)\u00a0 This, of course, requires gdb with python crammed inside.\u00a0 It might … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[7],"tags":[27,58,31,57,128],"class_list":["post-281","post","type-post","status-publish","format-standard","hentry","category-debugging","tag-colors","tag-gaudy","tag-gdb","tag-pyflam","tag-shiny"],"_links":{"self":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/281","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/comments?post=281"}],"version-history":[{"count":7,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/281\/revisions"}],"predecessor-version":[{"id":290,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/posts\/281\/revisions\/290"}],"wp:attachment":[{"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/media?parent=281"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/categories?post=281"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.visophyte.org\/blog\/wp-json\/wp\/v2\/tags?post=281"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}