Ubuntu
gdcm package

  1. Bug #1243741
  2. Comment #5

Comment 5 for bug 1243741

Revision history for this message
David Favor (davidfavor) wrote :

Alright let's see if I can at least figure out the true source of this assertion, as Apache seems to have no direct linkage to glib.

First I hacked out two scripts...

lsofunique - prints all unique files of a process ala lsof.

lddflat - prints lib name for every internal reference.

Attached is the full output off - lddflat $(lsofunique apache2 | grep '\.so') | grep glib

The lines that pop out relate to PHP... as I suspected...

/usr/lib/php5/20121212/enchant.so /lib/x86_64-linux-gnu/libglib-2.0.so.0
/usr/lib/php5/20121212/imagick.so /lib/x86_64-linux-gnu/libglib-2.0.so.0
/usr/lib/php5/20121212/midgard2.so /lib/x86_64-linux-gnu/libglib-2.0.so.0
/usr/lib/php5/20121212/midgard2.so /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
/usr/lib/php5/20121212/rrd.so /lib/x86_64-linux-gnu/libglib-2.0.so.0
/usr/lib/php5/20121212/vtkgdcm.so /lib/x86_64-linux-gnu/libglib-2.0.so.0

I'll "turn off" all these modules, then turn them back on, one-by-one, to identify the culprit.

I'll update this ticket with the nefarious module throwing the assertion.