Hi, You can also use the cli command : show system core-dumps core-file-info detail <core-filename>
Regards, David David Roy Orange - IP Domestic Backbone - TAC Tel. +33(0)299876472 Mob. +33(0)685522213 Email. david....@orange-ftgroup.com JNCIE-M/T #703 ; JNCIS-ENT -----Message d'origine----- De : juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Scott T. Cameron Envoyé : mardi 1 mars 2011 15:02 À : juniper-nsp@puck.nether.net Objet : Re: [j-nsp] Debug vmcore files Here's an example below. You'll either need to use gdb on the box itself, or get/xcompile a powerpc-freebsd gdb. Again, without source, you're not going to get far. % tar zvxf /var/tmp/chassisd.core-tarball.4.tgz chassisd.core.4.gz juniper.conf.gz messages chassisd.info.4 juniper.conf.1.gz % gzip -d chassisd.core.4.gz % gdb /usr/sbin/chassisd chassisd.core.4 GNU gdb 6.5 [juniper_2006a_411] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-specifix.com-freebsd"...(no debugging symbols found) Reading symbols from /usr/lib/libddl-access.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libddl-access.so.1 Reading symbols from /usr/lib/libjipc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libjipc.so.1 Reading symbols from /usr/lib/libberkeley-db.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libberkeley-db.so.4 Reading symbols from /usr/lib/libthr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libthr.so.2 Reading symbols from /usr/lib/libisc.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libisc.so.2 Reading symbols from /usr/lib/libkvm.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libkvm.so.3 Reading symbols from /usr/lib/libfasic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfasic.so.1 Reading symbols from /usr/lib/libhsl2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhsl2.so.1 Reading symbols from /usr/lib/libcmb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcmb.so.1 Reading symbols from /usr/lib/libcnh.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcnh.so.1 Reading symbols from /usr/lib/libjpci.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libjpci.so.1 Reading symbols from /usr/lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libm.so.4 Reading symbols from /usr/lib/libfabric2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric2.so.1 Reading symbols from /usr/lib/libfabric1.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric1.so.1 Reading symbols from /usr/lib/libprovider.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprovider.so.1 Reading symbols from /usr/lib/libiic.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libiic.so.1 Reading symbols from /usr/lib/libcam.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcam.so.3 Reading symbols from /usr/lib/libsbuf.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libsbuf.so.3 Reading symbols from /usr/lib/libutil.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libutil.so.5 Reading symbols from /usr/lib/libgcc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcc.so.1 Reading symbols from /usr/lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.6 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/libexec/ld-elf.so.1 Core was generated by `chassisd'. Program terminated with signal 6, Aborted. #0 0x42683428 in kill () from /usr/lib/libc.so.6 [New Thread 0x2057000 (LWP 100110)] (gdb) bt #0 0x42683428 in kill () from /usr/lib/libc.so.6 #1 0x421d8a30 in raise () from /usr/lib/libthr.so.2 #2 0x42681e88 in abort () from /usr/lib/libc.so.6 #3 0x01c00c64 in vlogging_event () #4 0x01c00af4 in vlogging () #5 0x01c00ce4 in logging () #6 0x01ab9670 in pic_clean_init () #7 0x01a16308 in mcontrol_check_backup_active () #8 0x01a16e20 in msm_exec () #9 0x01a17b2c in mcontrol_init () #10 0x019365e4 in ch_init () #11 0x01938640 in ch_a2_fru_map_set_context () #12 0x01ab3620 in allocadupx () #13 0x01ab44bc in main () (gdb) x 0x01a16308 0x1a16308 <mcontrol_check_backup_active+364>: 0x3d200201 On Tue, Mar 1, 2011 at 7:29 AM, meryem Z <merye...@hotmail.com> wrote: > You mean kgdb i guess. this tool is available on juniper routers on > /var/bin. > I'm wondering if anyone has tested it before ? > > > Thank you. > > > > > > > From: routeh...@gmail.com > > Date: Tue, 1 Mar 2011 07:21:58 -0500 > > To: juniper-nsp@puck.nether.net > > Subject: Re: [j-nsp] Debug vmcore files > > > > > You could use gdb. But the likelihood of any success without source > > code > is > > slim. > > > > You're better off sending them to jtac. > > > > On Tue, Mar 1, 2011 at 6:36 AM, meryem Z <merye...@hotmail.com> wrote: > > > > > > > > Hello community, > > > > > > Is there any tool to debug vmcore files generated on an m-series > juniper > > > router ? > > > > > > > > > Thanks. > > > > > > > > > > > > _______________________________________________ > > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > _______________________________________________ > > juniper-nsp mailing list juniper-nsp@puck.nether.net > > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ******************************************************************************** _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
