in reply to SEGVs building Perl 5.10 on Solaris 10?

Presumably, the applicable ulimits are not (too) restrictive ?

If nothing else crops up, it might be worthwhile downloading & installing the SUNWscat package - which will give you extended crash analysis capability on the generated core file - which is a useful tool to have on a Solaris box anyway.

If you're interested, I can recommend 'Panic! Unix System Crash Dump Analysis' by Drake & Brown - it does have a leaning toward (rather old, but nontheless pertinent) Solaris, but seeks to maintain a general approach - I got my copy, 2nd hand, via Amazon UK.

Update:

Added book ref.

A user level that continues to overstate my experience :-))

Replies are listed 'Best First'.
Re^2: SEGVs building Perl 5.10 on Solaris 10?
by Llew_Llaw_Gyffes (Scribe) on Apr 24, 2009 at 13:25 UTC
    Applicable ulimits shouldn't be a problem, as I'm working as root at the moment. The SUNWscat pointer is a useful one, and I shall try it right away to see whether it sheds any light. Thanks. :)
      Presumably, you've already been down the truss(1M) road in an attempt to identify the root cause ...

      A user level that continues to overstate my experience :-))
        Yes. Truss tells me it's an out-of-bounds address fault, apparently just after opening lib/strict.pm:
        read(3, " # ! . / m i n i p e r l".., 4096) = 4096 stat("lib/strict.pmc", 0xFFFFFD7FFFDFD710) Err#2 ENOENT stat("lib/strict.pm", 0xFFFFFD7FFFDFD670) = 0 open("lib/strict.pm", O_RDONLY) = 4 ioctl(4, TCGETA, 0xFFFFFD7FFFDFD430) Err#25 ENOTTY lseek(4, 0, SEEK_CUR) = 0 brk(0x00757EC0) = 0 brk(0x0075BEC0) = 0 read(4, " p a c k a g e s t r i".., 4096) = 3716 brk(0x0075BEC0) = 0 brk(0x0075FEC0) = 0 brk(0x0075FEC0) = 0 brk(0x00763EC0) = 0 lseek(4, 878, SEEK_SET) = 878 lseek(4, 0, SEEK_CUR) = 878 close(4) = 0 Incurred fault #6, FLTBOUNDS %pc = 0x004C2F24 siginfo: SIGSEGV SEGV_MAPERR addr=0x004C2F24 Received signal #11, SIGSEGV [default] siginfo: SIGSEGV SEGV_MAPERR addr=0x004C2F24
        ...but doesn't really shed any light on why I'm getting an address fault there. I was hoping someone else had tried this build or a similar combination, run into the same problem, and knew a simple configuration change to solve it.