"kdb" is only for analysing system core files. Might it be that this is an application core? If so, use "adb", not "kdb".
Quote:
Originally Posted by Sachin1987
The errors (wrong magic number and version mismatch) suggest you are analysing the dump on a system with different versions than the one where the dump was created. You need identical versions to be able to analyse the dump correctly.
I am using gdb to examine a core file but the output contains only the method addresses in hex.
Is there anyway to translate these addresses to a human-readable form? :confused: (0 Replies)
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Hi all,
I was hoping someone can point me in the right direction. I'm trying to filter out errors from a web log- any lines with ERROR in it. I know I could simply use the grep command to do this. However, there are times when a stack trace follows the error line. I would like to capture these... (2 Replies)
Hi all,
One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into... (9 Replies)
I'm on solaris 8. I need to check the stack trace inside my C program. I don't have printstack or walkstack. I tested getcontext and it works. But how do I get the symbols from "stack_t" ? Help please. Many thanks! (4 Replies)
Hello ,
I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV.
On my system only mdb works. Please help me to retrieve the stack trace from this core file.
I am novice to mdb and its nuaunces. Please help me with... (2 Replies)
Hi All
Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable -
#! /bin/bash
error_exit()
{
echo "======================="
echo $1
echo... (4 Replies)
I have a C program which is running as daemon and has some threads.
The program is running on dual core cpu and it may happen that different threads may run on different cpu core.
The problem is sometimes it crashes with some heap memory corruption probably between threads.
GDB command(t a a... (2 Replies)
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it.
To get the files that needs to... (6 Replies)
Discussion started by: chipmunken
6 Replies
LEARN ABOUT DEBIAN
catalyst::plugin::stacktrace
Catalyst::Plugin::StackTrace(3pm) User Contributed Perl Documentation Catalyst::Plugin::StackTrace(3pm)NAME
Catalyst::Plugin::StackTrace - Display a stack trace on the debug screen
SYNOPSIS
use Catalyst qw/-Debug StackTrace/;
DESCRIPTION
This plugin will enhance the standard Catalyst debug screen by including a stack trace of your appliation up to the point where the error
occurred. Each stack frame is displayed along with the package name, line number, file name, and code context surrounding the line number.
This plugin is only active in -Debug mode by default, but can be enabled by setting the "enable" config option.
CONFIGURATION
Configuration is optional and is specified in MyApp->config->{stacktrace}.
enable
Allows you forcibly enable or disalbe this plugin, ignoring the current debug setting. If this option is defined, its value will be used.
context
The number of context lines of code to display on either side of the stack frame line. Defaults to 3.
reverse
By default, the stack frames are shown in from "top" to "bottom" (newest to oldest). Enabling this option reverses the stack frames so they
will be displayed "bottom" to "top", or from the callers perspective.
verbose
This option sets the amount of stack frames you want to see in the stack trace. It defaults to 0, meaning only frames from your
application's namespace are shown. You can use levels 1 and 2 for deeper debugging.
If set to 1, the stack trace will include frames from packages outside of your application's namespace, but not from most of the Catalyst
internals. Packages ignored at this level include:
Catalyst
Catalyst::Action
Catalyst::Base
Catalyst::Dispatcher
Catalyst::Engine::*
Catalyst::Plugin::StackTrace
Catalyst::Plugin::Static::Simple
NEXT
main
If set to 2, the stack trace will include frames from everything except this module.
INTERNAL METHODS
The following methods are extended by this plugin.
execute
In execute, we create a local die handler to generate the stack trace.
finalize_error
In finalize_error, we inject the stack trace HTML into the debug screen below the error message.
setup
SEE ALSO
Catalyst
AUTHORS
Andy Grundman, <andy@hybridized.org>
Matt S. Trout, <mst@shadowcatsystems.co.uk>
THANKS
The authors of CGI::Application::Plugin::DebugScreen, from which a lot of code was used.
COPYRIGHT
Copyright (c) 2005 - 2009 the Catalyst::Plugin::StackTrace "AUTHORS" as listed above.
LICENSE
This program is free software, you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2009-10-18 Catalyst::Plugin::StackTrace(3pm)