Opened 14 years ago
Closed 13 years ago
#29412 closed defect (fixed)
gettext 0.18.1.1 - conftest crash
Reported by: | tael67@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | tiger | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: | gettext |
Description
When trying to build gettext, I have an OSX crash popup for conftest. Here is the log :
Date/Time: 2011-05-10 02:34:25.031 +0200 OS Version: 10.4.11 (Build 8S2167) Report Version: 4 Command: conftest Path: ./conftest Parent: sh [27470] Version: ??? (???) PID: 27471 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000 Thread 0 Crashed: 0 libSystem.B.dylib 0x9003e9e0 realpath + 240 1 conftest 0x00001f2a main + 36 2 conftest 0x00001eea _start + 216 3 conftest 0x00001e11 start + 41 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00000000 ebx: 0x9003e901 ecx: 0xffffffff edx: 0x90004ddc edi: 0x00000000 esi: 0x00001fc8 ebp: 0xbffff5b8 esp: 0xbfffe310 ss: 0x0000001f efl: 0x00010246 eip: 0x9003e9e0 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 Binary Images Description: 0x1000 - 0x1fff conftest /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gettext/work/gettext-0.18.1.1/gettext-runtime/conftest 0x8fe00000 - 0x8fe4afff dyld 46.16 /usr/lib/dyld 0x90000000 - 0x90171fff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x901c1000 - 0x901c3fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib 0x90bd2000 - 0x90bd9fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib Model: MacBook2,1, BootROM MB21.00A5.B07, 2 processors, Intel Core 2 Duo, 2 GHz, 1 GB Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.4.4 Bluetooth: Version 1.9.5f4, 2 service, 0 devices, 1 incoming serial ports Network Service: AirPort, AirPort, en1 Serial ATA Device: ST980811AS, 74.53 GB Parallel ATA Device: MATSHITACD-RW CW-8221 USB Device: USB2.0 Hub, Up to 480 Mb/sec, 500 mA USB Device: iPod, Apple, Up to 480 Mb/sec, 500 mA USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA USB Device: Macally DotMouse, Macally Peripherals, Up to 1.5 Mb/sec, 500 mA USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
Change History (5)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 14 years ago by tael67@…
I have updated to 1.9.2 and it still crashes. But you are right, it does not prevent gettext from being installed.
comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
This particular crash is in realpath. Within the gettext source there is the file canonicalize.m4 which is built into the configure script which tests for the capabilities of the realpath function; it seems to be this test which is crashing and thus showing a crash reporter dialog box. Perhaps the other ports you've seen to display a crash reporter dialog box are using the same canonicalize.m4 test. Or perhaps they are unrelated crashes.
In this case anyway, I've reported the problem to the developers of gettext: https://savannah.gnu.org/bugs/?33273 . For other ports, you should report the problems directly to the developers; there's likely nothing MacPorts-specific about the problem, and MacPorts will get the fix as the upstream developers release new versions.
Be aware that support for Tiger, both in MacPorts and in the developer community, is waning as fewer people have access to Tiger machines anymore.
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Upstream has fixed this in gnulib, so I'm marking this "fixed" (though it's not fixed in MacPorts yet). The fix will trickle down to MacPorts in time, once a new version of gnulib is released, and a new version of gettext is released based on that version of gnulib, and the gettext port in MacPorts is updated to that new version of gettext.
That sounds familiar. But does it actually prevent gettext from building?
P.S.: if you're really running MacPorts 1.9.1, please "sudo port selfupdate" to get 1.9.2.