≡

wincent.dev

  • Products
  • Blog
  • Wiki
  • Issues
You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.
Home » Issues » Bug #2150

Bug #2150: SEGV from Command-T

Kind bug
Product Command-T
When Created 2014-01-21T14:44:01Z, updated 2014-01-22T06:10:47Z
Status closed
Reporter Andri Moell
Tags no tags

Description

Just ugpraded from 89896bd to f9d168c, compiled and now CommandT's bundle is SEGVing with the top of the stack looking as such:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff8878ad46 __kill + 10
1   Vim                           	0x00000001024a4698 mch_exit + 216
2   Vim                           	0x00000001024a75fe deathtrap + 526
3   libsystem_c.dylib             	0x00007fff8869990a _sigtramp + 26
4   libruby.1.dylib               	0x00000001029545d9 st_lookup + 24
5   libruby.1.9.1.dylib           	0x000000010452626c rb_intern3 + 140
6   ext.bundle                    	0x00000001044afff6 CommandT_option_from_hash + 61
7   ext.bundle                    	0x00000001044b05b5 CommandTMatcher_initialize + 92
8   libruby.1.dylib               	0x00000001028fe5f9 0x1028d9000 + 153081

Comments

  1. Andri Moell 2014-01-21T15:00:28Z

    My bad. Turns out this was a system configuration issue of extconf.rb finding the newer Ruby in /usr/local/bin and not using the system's v1.8.7. Jeesh the shit we have to deal with as developers.

    PS. I'm not sure I can close this issue myself...

  2. Greg Hurrell 2014-01-22T06:10:44Z

    Excellent. Glad to hear you got it sorted out.

  3. Greg Hurrell 2014-01-22T06:10:47Z

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

  • contact
  • legal

Menu

  • Blog
  • Wiki
  • Issues
  • Snippets