pro64-support
[Top] [All Lists]

Re: The long loading time of .so of Pro64 under GDB

To: "Wu Chengyong" <cwu@xxxxxxxxx>
Subject: Re: The long loading time of .so of Pro64 under GDB
From: "Andi Kleen" <ak@xxxxxxx>
Date: Wed, 20 Sep 2000 11:37:48 +0200
Cc: <pro64-support@xxxxxxxxxxx>, "Zhang Zhaoqing" <zqzhang@xxxxxxxxx>, "Ju, Roy" <roy.ju@xxxxxxxxx>, "Liu Yang" <ly@xxxxxxxxx>, "Lian Ruiqi" <lrq@xxxxxxxxx>, "Gan Ge" <gange@xxxxxxxxx>, "Fu Chen" <cfu@xxxxxxxxx>, "Feng Xiaobing" <fxb@xxxxxxxxx>, "Dong Xiqian" <dxq@xxxxxxxxx>, "Gao Lin" <gl@xxxxxxxxx>
In-reply-to: <00fe01c022c6$6310faa0$b628e29f@ACTMISC>; from cwu@xxxxxxxxx on Wed, Sep 20, 2000 at 01:48:22PM +0800
References: <00fe01c022c6$6310faa0$b628e29f@ACTMISC>
Sender: owner-pro64-support@xxxxxxxxxxx
On Wed, Sep 20, 2000 at 01:48:22PM +0800, Wu Chengyong wrote:
> Hi, everyone,
> 
> We are tracing and analyzing Pro64 using GDB.
> But we experienced a very long loading time when GDB try to load some .so 
> (e.g. be.so, cg.so, ...).
> In our environment it needs about 40 minutes - 1 hour to load the symbol 
> tables of these two .so.
> We use GCC 2.95.2 to compile Pro64 (version 0.01.0-10) and we modified 
> ../osprey1.0/Makefile.gsetup
> to add debugging information into those .so.

Your machine is probably heavily swapping/trashing because gdb needs so much
memory. You can check its memory use with running top during the load.
gdb also deals very poorly with very big symbol tables (and worse with big 
C++ programs which have very long symbol names too). An useful resource is 
http://www.mozilla.org/unix/debugging-faq.html , it explains some techniques
that may help.



-Andi

<Prev in Thread] Current Thread [Next in Thread>