[TxMt] Re: Python bundle - 2 problems

Getzen jim at getzen.name
Tue Feb 24 23:22:21 UTC 2009



Alex Ross-8 wrote:
> 
> Well, I am not experiencing that problem here.  Do you have any crash  
> logs from textmate or from tm_dialog2 in ~/Library/Logs?
> 
The only log in that location is textmate-io-exhaust.log.
Here is the report text from the tm_dialog2 crash:

Process:         tm_dialog2 [343]
Path:           
/Applications/TextMate.app/Contents/PlugIns/Dialog2.tmplugin/Contents/Resources/tm_dialog2
Identifier:      tm_dialog2
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  Python [341]

Date/Time:       2009-02-24 18:18:37.840 -0500
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000008318
Crashed Thread:  0

Thread 0 Crashed:
0   dyld                          	0x8fe13b9d
ImageLoaderMachO::preFetch(int, unsigned long long, ImageLoader::LinkContext
const&) + 109
1   dyld                          	0x8fe14be4
ImageLoaderMachO::ImageLoaderMachO(char const*, int, unsigned char const*,
unsigned long long, unsigned long long, stat const&,
ImageLoader::LinkContext const&) + 628
2   dyld                          	0x8fe05bec dyld::loadPhase5open(char
const*, dyld::LoadContext const&, std::vector<char const*,
std::allocator<char const*> >*) + 1036
3   dyld                          	0x8fe05f71 dyld::loadPhase4(char const*,
dyld::LoadContext const&, std::vector<char const*, std::allocator<char
const*> >*) + 161
4   dyld                          	0x8fe06105 dyld::loadPhase2(char const*,
dyld::LoadContext const&, char const* const*, char const* const*,
std::vector<char const*, std::allocator<char const*> >*) + 325
5   dyld                          	0x8fe069e1 dyld::loadPhase1(char const*,
dyld::LoadContext const&, std::vector<char const*, std::allocator<char
const*> >*) + 209
6   dyld                          	0x8fe06a73 dyld::loadPhase0(char const*,
dyld::LoadContext const&, std::vector<char const*, std::allocator<char
const*> >*) + 67
7   dyld                          	0x8fe06bd2 dyld::load(char const*,
dyld::LoadContext const&) + 130
8   dyld                          	0x8fe06df8 dyld::libraryLocator(char
const*, bool, bool, char const*, ImageLoader::RPathChain const*) + 72
9   dyld                          	0x8fe0f22d
ImageLoader::recursiveLoadLibraries(ImageLoader::LinkContext const&,
ImageLoader::RPathChain const&) + 557
10  dyld                          	0x8fe0f13f
ImageLoader::recursiveLoadLibraries(ImageLoader::LinkContext const&,
ImageLoader::RPathChain const&) + 319
11  dyld                          	0x8fe1057e
ImageLoader::link(ImageLoader::LinkContext const&, bool, bool,
ImageLoader::RPathChain const&) + 62
12  dyld                          	0x8fe051ae dyld::link(ImageLoader*, bool,
ImageLoader::RPathChain const&) + 158
13  dyld                          	0x8fe07acf dyld::_main(mach_header
const*, unsigned long, int, char const**, char const**, char const**) + 2831
14  dyld                          	0x8fe01872
dyldbootstrap::start(mach_header const*, int, char const**, long) + 818
15  dyld                          	0x8fe01037 _dyld_start + 39

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00008324  ebx: 0x8fe13b44  ecx: 0x8fe3267c  edx: 0x00001000
  edi: 0x00006000  esi: 0x00007414  ebp: 0xbfffac38  esp: 0xbfffabd0
   ss: 0x0000001f  efl: 0x00010206  eip: 0x8fe13b9d   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00008318

Binary Images:
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5>
/usr/lib/dyld


Alex Ross-8 wrote:
> 
> If you try a  
> simple ruby script with contents “gets” do you also get the crash,  
> or is it only for python?
> 
No, a Ruby 'gets' works fine.

Jim
-- 
View this message in context: http://www.nabble.com/Python-bundle---2-problems-tp22163059p22192985.html
Sent from the textmate users mailing list archive at Nabble.com.




More information about the textmate mailing list