I've been running debug enabled tmux 2.0 for weeks and it hasn't crashed so
far. Perhaps it was a bug in tmux 1.9.
On Thu, Oct 30, 2014 at 11:48 AM, Il Memming Park wrote:
> Thank you for the kind instructions. I'll report back soon.
>
> Memming
> On Oct 30, 2014
new -d
> $ gdb -q tmux `pgrep tmux`
> (gdb) c
>
> Then do "tmux a" from another window and reproduce. When it crashes, go
> back to the gdb window and do "bt full" and show me the output.
>
>
> On Thu, Oct 30, 2014 at 05:29:45AM -0500, Il Memming Park wro
No. It didn't leave a dump. How would I obtain one? Fire up gdb?
Thanks.
Memming
On Oct 30, 2014 3:19 AM, "Nicholas Marriott"
wrote:
> Do you have a backtrace?
>
>
> On Sat, Oct 25, 2014 at 02:19:59PM -0500, Il Memming Park wrote:
> >Hi all,
> >
Hi all,
I'm using tmux 1.9a on Mac OS (13.4.0), homebrew version. I use it with ViM
REPL environment called slimux (https://github.com/epeli/slimux). As far as
I understand it sends selected text via calling 'tmux set-buffer' and 'tmux
paste-buffer -t'.
It works great, but after some extensive buf
