[nsp] traceback

Richard Gallagher rgallagh@cisco.com
Thu, 22 Aug 2002 09:58:02 +0200


Or if you have the right access to CCO you can use the stack decoder, it 
works with tracebacks too! Just add the show ver and the error. Saves 
openeing a case!!

http://www.cisco.com/cgi-bin/Support/Stackdecoder/stackdecoderinput.pl

Rich

Jared Mauch wrote:
> 	You need to send it to the tac/cisco.
> 
> 	they will then use the symbol files to map the hex numbers (PC)
> to the function-name and address within that function that caused the
> error.
> 
> 	- Jared
> 
> On Thu, Aug 22, 2002 at 07:38:08AM +0200, odusseus wrote:
> 
>>Hi,
>>
>>I would like to know if there is a way to understand a traceback message or if the only solution is to send it to the Cisco TAC ?
>>
>>Thank you,
>>
>>Regards.
>>
>>Christophe
>>------------------------------------------
>>
>>Faites un voeu et puis Voila ! www.voila.fr
>>
>>_______________________________________________
>>cisco-nsp mailing list  real_name)s@puck.nether.net
>>http://puck.nether.net/mailman/listinfo/cisco-nsp
>>archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 


-- 

#------------------------------------------------------------------#
#    _.|._.|._    | Richard Gallagher  | Direct: +32 2 704 5421    #
#  Cisco Systems  | CCIE #7211         | Email: rgallagh@cisco.com #
#------------------------------------------------------------------#