Server hung, is this a stack trace? Post: 302885947

10 More Discussions You Might Find Interesting

1. Programming

Core file without a readable stack trace

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:

2. Programming

printing a stack trace with backtrace

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++.

3. UNIX for Advanced & Expert Users

help required - stack trace

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...

4. Filesystems, Disks and Memory

get stack trace from C program on Solaris 8

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!

5. Solaris

Need to retrieve stack trace from core using mdb

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...

6. AIX

How to get the stack trace using kdb?

Hi All, I am trying to debug my core file using kdb. When I try to get the stack trace I am facing this error. core mapped from @ 700000000000000 to @ 70000000306fc04 Preserving 1680415 bytes of symbol table Dump does not start with valid magic number WARNING: Possibly truncated or...

7. Shell Programming and Scripting

Stack Trace

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...

8. UNIX for Dummies Questions & Answers

View User Mode Call Stack of Hung Process

I have a multithreaded usermode program(actually a daemon) which is in hanged state. To debug it I tried attaching the process to gdb, but the gdb hangs. gstack also gets hanged. I peeped into the proc file system and saw the process to be in sleeping state. /proc/sysrq-trigger I guess...

9. Programming

View Stack Trace of different cores

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...

10. Shell Programming and Scripting

Java stack trace parser in awk

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...

LEARN ABOUT FREEBSD

asr

ASR(4)							   BSD Kernel Interfaces Manual 						    ASR(4)

NAME

     asr -- driver for Adaptec I2O based SCSI/ATA host bus adapters

SYNOPSIS

     device asr

DESCRIPTION

     The Adaptec asr driver provides access to disks and disk arrays controlled by I2O based host bus adapters and SmartRAID SCSI RAID adapters
     through the standard SCSI disk da(4) interface.

     The supported adapters provide 64 bit PCI, Compact PCI, Zero Channel PCI, and up to four channels of Ultra2, Ultra 160, or Ultra320 SCSI, or
     two channels of 1GB Fibre.  All support RAID-0, RAID-1, RAID-10, RAID-5 and RAID-50 arrays.  All SCSI target types are supported.	For the
     ATA based controllers, one IDE drive per channel is supported.  Hot-swapping of IDE drives is not supported at this time.

     All host bus adapters must be configured before they can be used with any operating system.  Please contact Adaptec directly to obtain the
     latest information on configuration utilities for the adapters.  Currently there are both a Motif based GUI configuration utility and a CLI
     based configuration utility available from the Adaptec Web site.  The cards and arrays can also be configured via the BIOS based configura-
     tion tool (SMOR).

HARDWARE

     The adapters currently supported by the asr driver include the following:

     o	 Adaptec Zero-Channel SCSI RAID 2000S, 2005S, 2010S, 2015S
     o	 Adaptec SCSI RAID 2100S, 2110S
     o	 Adaptec ATA-100 RAID 2400A
     o	 Adaptec SCSI RAID 3200S, 3210S
     o	 Adaptec SCSI RAID 3400S, 3410S
     o	 Adaptec SmartRAID PM1554
     o	 Adaptec SmartRAID PM1564
     o	 Adaptec SmartRAID PM2554
     o	 Adaptec SmartRAID PM2564
     o	 Adaptec SmartRAID PM2664
     o	 Adaptec SmartRAID PM2754
     o	 Adaptec SmartRAID PM2865
     o	 Adaptec SmartRAID PM3754
     o	 Adaptec SmartRAID PM3755U2B / SmartRAID V Millennium
     o	 Adaptec SmartRAID PM3757
     o	 DEC KZPCC-AC (LVD 1-ch, 4MB or 16MB cache), DEC KZPCC-CE (LVD 3-ch, 64MB cache), DEC KZPCC-XC (LVD 1-ch, 16MB cache), DEC KZPCC-XE (LVD
	 3-ch, 64MB cache) -- rebadged SmartRAID V Millennium

FILES

     /dev/asr*	Adaptec SCSI RAID control nodes

NOTES

     The ATA based controllers present their devices as SCSI-like devices via CAM.  For IDE drives attached to these cards, a subset of standard
     SCSI commands and mode pages are understood via translation performed in the card's firmware.

SEE ALSO

     da(4)

HISTORY

     The asr (Adaptec SCSI RAID) driver first appeared as the dpti2o driver under BSDi BSD/OS 3.2, then under FreeBSD 2.2.8 and was ported over to
     the CAM layer represented in 4.0.

AUTHORS

     The asr driver was kindly donated by Adaptec and is maintained by Mark Salyzyn <mark_salyzyn@adaptec.com>.  This manual page was written by
     Mark Salyzyn and fixed up by Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>.

BSD
								   July 14, 2004							       BSD