Mike Hommey wrote:
Can you try to run the following:
cd /usr/lib/xulrunner-1.9
./run-mozilla.sh -g ./xpcshell -e ""
gdb> run
When it hangs, press CTRL+C
gdb> bt full

Then, please send the result here.

There is no trace. GDB says "program exited normally":
##
/usr/lib/xulrunner-1.9# ./run-mozilla.sh -g ./xpcshell -e ""
MOZILLA_FIVE_HOME=.
 LD_LIBRARY_PATH=.:./plugins:.
DISPLAY=:0.0
DYLD_LIBRARY_PATH=.:.
    LIBRARY_PATH=.:./components:.
      SHLIB_PATH=.:.
         LIBPATH=.:.
      ADDON_PATH=.
     MOZ_PROGRAM=./xpcshell
     MOZ_TOOLKIT=
       moz_debug=1
    moz_debugger=
/usr/bin/gdb ./xpcshell -x /tmp/mozargs.S21326
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb)
(gdb) run
Starting program: /usr/lib/xulrunner-1.9/xpcshell '-e' ''
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb64bf720 (LWP 21338)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb63f9b90 (LWP 21341)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread 0xb63f9b90 (LWP 21341) exited]

Program exited normally.
(gdb) bt full
No stack.
##

But if i start without "-g", it hangs.

I did further debugging and found that the script hangs on line 168 of run-mozilla.sh.
##
LD_PRELOAD="${LD_PRELOAD+$LD_PRELOAD:}$MOZILLA_FIVE_HOME/libjemalloc.so" "$prog" ${1+"$@"}
##
An echo after this line doesn't returns.

I am using libtrash here on my system and the variable LD_PRELOAD is set to:
##
echo $LD_PRELOAD
/usr/lib/libtrash/libtrash.so.2.4
##

The installation process doesn't hangs, if i unset the LD_PRELOAD variable before. Do you have any explanation why the line 168 making problems?

Regards,
 Sumit



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to