[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#617759: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc



found 617759 eglibc/2.13-7
quit

Aurelien Jarno wrote:

> Have you been able to reproduce the issue in a VM? If yes, could you
> please share it? I am still unable to reproduce it.

Alas, no, I still haven't reproduced it in a VM.  My laptop with
Debian libc6 2.13-7 and icedove 3.1.10-2 still reproduces it:

| $ icedove
| /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

I suspect it's timing sensitive, which might explain why I could
reproduce it on real hardware but not a vm.  For example:

| $ LD_DEBUG=unused icedove
|      29640:	/usr/lib/icedove/icedove-bin: error: symbol lookup error: undefined symbol: nspr_use_zone_allocator (fatal)
|      29640:	/usr/lib/icedove/icedove-bin: error: symbol lookup error: undefined symbol: gtk_widget_device_is_shadowed (fatal)
|      29640:	/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
|      29640:	/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: gtk_widget_device_is_shadowed (fatal)
|      29640:	/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: error: symbol lookup error: undefined symbol: gtk_module_display_init (fatal)
|      29640:	/usr/lib/icedove/components/libdbusservice.so: error: symbol lookup error: undefined symbol: NS_Alloc (fatal)
| /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc

I'm going to sleep soon; tomorrow I'll try reproducing with eglibc +
Debian patches again.  If you have any crazy ideas for things to try
(e.g., what to printf), I'll do what I can.  I suspect the backtrace I
sent before would be a good place to start for someone familiar with
XPCOM.

Sorry to leave this hanging for so long.
Jonathan



Reply to: