Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#2075 closed defect (fixed)

Browse in v.in.ogr and r.in.gdal causes entire GUI to crash

Reported by: cmbarton Owned by: grass-dev@…
Priority: critical Milestone: 7.0.0
Component: wxGUI Version: svn-trunk
Keywords: Cc:
CPU: Unspecified Platform: MacOSX

Description

This problem is relatively new (past month or so). Clicking the browse button in the GUI wrappers for v.in.ogr and r.in.gdal causes the entire GUI to crash. Because the whole thing crashes, there are no GRASS error messages. Here is what I hope is the relevant portion of the system crash message:

Process:         Python [26361]
Path:            /System/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python
Identifier:      org.python.python
Version:         2.6.7 (2.6.7)
Build Info:      python-60004000000000~1
Code Type:       X86 (Native)
Parent Process:  Python [26160]
User ID:         501

PlugIn Path:       /Users/USER/*/GRASS-7.0.app/Contents/MacOS/lib/libwx_macud-2.8.0.dylib
PlugIn Identifier: libwx_macud-2.8.0.dylib
PlugIn Version:    ??? (9)

Date/Time:       2013-09-11 15:49:55.092 -0700
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version:  10

Interval Since Last Report:          5028416 sec
Crashes Since Last Report:           948
Per-App Interval Since Last Report:  8688 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      5872B1C9-EF11-8711-7280-A91E040454E2

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffff4

Change History (3)

comment:1 Changed 6 years ago by annakrat

Please try r57642. There was a wrong wildcard format which was happily ignored on Linux. But definitely there is something wrong in wxPython on Mac because such a minor issue shouldn't crash the whole gui.

comment:2 Changed 6 years ago by cmbarton

Resolution: fixed
Status: newclosed

Fixed! Thanks. I agree that there is something weird going on. I wonder if it goes away when I stop compiling for 10.6 compatibility?

Michael

comment:3 in reply to:  2 Changed 6 years ago by annakrat

Replying to cmbarton:

Fixed! Thanks. I agree that there is something weird going on. I wonder if it goes away when I stop compiling for 10.6 compatibility?

Most probably not. Anyway, it's fixed now.

Note: See TracTickets for help on using tickets.