On 1/8/14 3:00 PM, Alvaro Herrera wrote:
> Marko Tiikkaja wrote:
>>
>> #0 0x00007f26dd17d5b7 in monstartup () from /lib/x86_64-linux-gnu/libc.so.6
>> #1 0x00007f26d79e5c70 in ?? ()
>> #2 0x00007f26d79e5c80 in ?? ()
>> #3 0x00007f254d772b60 in ?? ()
>> #4 0x00000000006359c5 in LWLockAcquire (lockid=87, mode=LW_SHARED)
>> at /build/buildd/postgresql-9.1-9.1.9/build/../src/backend/storage/lmgr/lwlock.c:464
>
> Hm, looks like either they got stuck trying to activate profiling (but
> then Debian doesn't build its packages with gcc -pg, does it?), or the
> backtrace is flawed for those upper frames. Maybe installing the libc
> -dbg (I imagine it'd be libc6-dbg) package would be useful, if this
> reoccurs.
libc6-dbg only changed it a bit:
#0 0x00007f26dd17d5b7 in __monstartup (lowpc=<optimized out>,
highpc=140737090958784) at gmon.c:130
#1 0x00007f26d79fcae0 in ?? ()
#2 0x00007f26d79fcaf0 in ?? ()
#3 0x00007f254d772aa0 in ?? ()
I still have the core dump available, is there something else I can do?
From what I heard, this is the second time this happened already :-(
Regards,
Marko Tiikkaja
