search

mattboehm / vim-unstack

Vim plugin for parsing stack traces and opening the files
286 stars 15 forks source link

"No stack trace found" for Go #23

Closed brighama closed 5 years ago

brighama commented 10 years ago

Not sure if I'm doing it right, but the following snippet gives me "No stack trace found" when I apply :UnstackFromSelection or :UnstackFromClipboard

goroutine 19 [finalizer wait]: runtime.park(0x4132d0, 0x65b178, 0x659ce9) /usr/local/go/src/pkg/runtime/proc.c:1369 +0x89 runtime.parkunlock(0x65b178, 0x659ce9) /usr/local/go/src/pkg/runtime/proc.c:1385 +0x3b runfinq() /usr/local/go/src/pkg/runtime/mgc0.c:2644 +0xcf runtime.goexit() /usr/local/go/src/pkg/runtime/proc.c:1445

mattboehm commented 10 years ago

Sorry for the delay in getting back to you. It's working for me locally, so here's a few things to check:

  1. Vim should be compiled with clipboard support. If you run :version, you should see "+clipboard"

  2. g:unstack_extractors should include the go extractor (it does this by default as long as you didn't edit it in your dotfiles. To test this, you can run :echom string(g:unstack_extractors) and confirm that it includes:

    {'regex': '\v^[ \t]*(.+):(\d+) +0x\x+$', 'file_replacement': '\1', 'extract': function('276'), 'line_replacement': '\2'}

If these don't help, let me know and we can look into other issues.

mattboehm commented 5 years ago

Closing this as I've never heard back and was unable to reproduce this locally, but if anyone is still running into this issue, please let me know.