Re: How to enable the debug symbols

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

 



Hi Simon!

A couple things come to mind:
1. Are you using the same prefix now as you had when /usr/local/lib/libceph.so.1 was built? 2. Does the timestamp of the /usr/local/lib/libceph.so.1 change after you ran make install? 3. Try deleting /usr/local/lib/libceph.so.1 (or move it to some other folder) and then ./configure, make, make install.


Thanks,
Dyweni



On Tue, 17 May 2011 11:29:37 +0800, Simon Tian wrote:

Well, I tried all these:
1) ./configure #(with desired environment settings)
2) ./autogen.sh
2.5) make clean
3) make -j 14

1) ./configure #(with desired environment settings)
2) ./autogen.sh
2.5) make clean
2.6ïmake uninstall
3) make -j 14

1) ./autogen.sh
2) ./configure #(with desired environment settings)
2.5) make clean
2.6ïmake uninstall
3) make -j 14

0.5)tar zxvf ceph-0.27.1.tar.gz
1) ./configure #(with desired environment settings)
2) ./autogen.sh
2.6ïmake uninstall
3) make -j 14

The result is all the same:

============================================================================
Breakpoint 1, ceph_write (fd=10, buf=0x7fff76bf0120 "", size=2097152,
offset=0) at libceph.cc:322
322 return client->write(fd, buf, size, offset);
(gdb)
(gdb) c
Continuing.

Breakpoint 3, 0x00007fa7a61f8c32 in ?? () from
/usr/local/lib/libceph.so.1
^^^^^
(gdb) info b
Num Type Disp Enb Address What
1 breakpoint keep y 0x00007fa7a61ca20f in ceph_write at
libceph.cc:322
breakpoint already hit 1 time
2 breakpoint keep y 0x00007fa7a61ca20f in ceph_write at
libceph.cc:321
breakpoint already hit 1 time
3 breakpoint keep y 0x00007fa7a61f8c32 client/Client.cc:4999
breakpoint already hit 1 time
(gdb)

============================================================================

Seem like no symbol for client/Client.cc.... Hmm, what do you think?
Makefile attached. FYI

2011/5/17 Sage Weil :
On Mon, 16 May 2011, Gregory Farnum wrote:

Did you actually re-build the code? Configure just sets up some of
the scripts: 1) ./configure #(with desired environment settings) 2)
./autogen.sh
2.5) make clean

3) make #(hopefully -j8 or something)
sage

Then you'll need to make sure that the built library is the one
you're linking with -- how to do this varies a bit depending on your
environment but probably the easiest way to do it is to run "make
install". -Greg On Mon, May 16, 2011 at 5:45 AM, Simon Tian wrote:

Hi, I tried ( CFLAGS="-march=x86_64 -pipe -ggdb"
CXXFLAGS="${CFLAGS}" ), but error comes:
======================================================
root@xxxxxxxxxxxxxxxxxxxxxxxxxxxx [1] # ./configure checking build
system type... x86_64-unknown-linux-gnu checking host system
type... x86_64-unknown-linux-gnu checking target system type...
x86_64-unknown-linux-gnu checking for a BSD-compatible install...
/usr/bin/install -c checking whether build environment is sane...
yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking
for gawk... gawk checking whether make sets $(MAKE)... yes checking
for style of include used by make... GNU checking for gcc... gcc
checking for C compiler default output file name... configure:
error: C compiler cannot create executables See `config.log' for
more details.
======================================================= So I tried
( CFLAGS="-pipe -ggdb" CXXFLAGS="${CFLAGS}" ), all the FLAGS in the
Makefile was set to "-pipe -ggdb", as the attachment showed.. Hmm,
but there was still "??" in the back trace: (gdb) bt #0
0x00007fd007491c32 in ?? () from /usr/local/lib/libceph.so.1 #1
0x00007fd00746322d in ceph_write (fd=10, buf=0x7fff4ffe2210 "",
size=2097152, offset=0) at libceph.cc:322 #2 0x0000000000400fd3 in
main (argc=1, argv=0x7fff501e23d8) at testceph.cc:72 There is a
exception when running my application with libceph, so I need the
stack in the libceph to point the problem. It's a little
URGENT...But I don't know what happened in the libceph, so
unlucky.....Here is my stack:




===================================================================================
(gdb) c Continuing. Program received signal SIGABRT, Aborted.
[Switching to Thread 0x40838940 (LWP 9118)] 0x000000312b630265 in
raise () from /lib64/libc.so.6 (gdb) bt #0 0x000000312b630265 in
raise () from /lib64/libc.so.6 #1 0x000000312b631d10 in abort ()
from /lib64/libc.so.6 #2 0x000000312debec44 in
__gnu_cxx::__verbose_terminate_handler () from
/usr/lib64/libstdc++.so.6 #3 0x000000312debcdb6 in ?? () from
/usr/lib64/libstdc++.so.6 #4 0x000000312debcde3 in std::terminate
() from /usr/lib64/libstdc++.so.6 #5 0x000000312debceca in
__cxa_throw () from /usr/lib64/libstdc++.so.6 #6 0x00007fdb4cce7a78
in ?? () from /usr/local/lib/libceph.so.1 #7 0x00007fdb4cbb4e1c in
Mutex::Lock (this=0x66d790, no_lockdep=false) at
./common/Mutex.h:118 #8 0x00007fdb4cbcf5f4 in ?? () from
/usr/local/lib/libceph.so.1 #9 0x00007fdb4cc45304 in ?? () from
/usr/local/lib/libceph.so.1 #10 0x00007fdb4cd2b1d5 in ?? () from
/usr/local/lib/libceph.so.1 #11 0x00007fdb4cbec038 in ?? () from
/usr/local/lib/libceph.so.1 #12 0x00007fdb4cc6101d in ?? () from
/usr/local/lib/libceph.so.1 #13 0x00007fdb4cc4862b in ?? () from
/usr/local/lib/libceph.so.1 #14 0x00007fdb4cbb8641 in ?? () from
/usr/local/lib/libceph.so.1 #15 0x00007fdb4cbf0a28 in ?? () from
/usr/local/lib/libceph.so.1 #16 0x000000312be064a7 in start_thread
() from /lib64/libpthread.so.0 #17 0x000000312b6d3c2d in clone ()
from /lib64/libc.so.6 (gdb)




===================================================================================
Thx! Simon 2011/5/15 Dyweni - Ceph-Devel :

Hi Simon! Set your CFLAGS and CXXFLAGS environment variables
before calling configure and make. Example: CFLAGS="-march=native
-pipe -ggdb" CXXFLAGS="${CFLAGS}" ./configure
CFLAGS="-march=native -pipe -ggdb" CXXFLAGS="${CFLAGS}" make etc
Thanks, Dyweni On Sun, 15 May 2011 20:37:16 +0800, Simon Tian
wrote:

Hi Dyweni, Can I do this by any options of "./configure"? or
JUST modify the Makefile manually? Thx! Simon
-- To unsubscribe from this list: send the line "unsubscribe
ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx [4] More majordomo info at http://vger.kernel.org/majordomo-info.html [5]


Links:
------
[1] mailto:root@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2] mailto:YS3fpFE2ykfB@xxxxxxxxxx
[3] mailto:aixt2006@xxxxxxxxx
[4] mailto:majordomo@xxxxxxxxxxxxxxx
[5] http://vger.kernel.org/majordomo-info.html
[6] mailto:sage@xxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux