12-30-2011
where is it that you are dumping?
--ahamed
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. Programming
how about asynchronous canceling?
or with signal?
if with signal whether it effects the process?
my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies
3. Programming
Could any one please suggest me how to solve this......
when I compiled the program and tried to execute it as follows, it works fine under different inputs like:
./main -r 300 -w 3 -s 100
./main -r 600 -w 3 -s 1000
./main -r 10 -w 3 -s 100
But it fails when I tired to give the input as... (1 Reply)
Discussion started by: kumars
1 Replies
4. Solaris
Hello,
I'm running a kill -QUIT on few process IDs (OS: Solaris) but the Thread Dump is empty.
Can you please help me get it back on?
Since I'm quite new to this, I'm not aware of the checks. Please let me know for the info required to debug this issue.
Thanks! (3 Replies)
Discussion started by: DevendraG
3 Replies
5. Linux
How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ?
i use pthread_setspecific to store some data in the pthread's local stoare.
my multi threaded program on linux crashed, and i want to see what is stored in current running thread's... (2 Replies)
Discussion started by: vishwasungal
2 Replies
cr_read(3) Library Functions Manual cr_read(3)
NAME
cr_read - read from crash dump
SYNOPSIS
DESCRIPTION
The function attempts to read the memory area defined by mem_page and num_pages into the buffer pointed to by buf from the crash dump
opened using crash_cb.
The starts at the position in the crash dump associated with the physical memory offset given by mem_page. If the physical memory page
mem_page does not exist in the crash dump, sets *num_pages to 0 and returns 0.
No data transfer will occur past a page of memory that does not exist in the crash dump. If the starting position, mem_page, plus the read
length, *num_pages, goes past an area of memory that does not exist in the crash dump, sets *num_pages to the number of consecutive pages
(starting at mem_page) actually read.
RETURN VALUE
Returns zero for success. Other possible return values are described in libcrash(5).
EXAMPLES
Assuming a process opened a crash dump, the following call to cr_read(3) reads the first pages from the crash dump into the buffer pointed
to by mybuf:
WARNINGS
may return fewer pages than requested due to implementation details. Always check the number of pages returned. If they are fewer than
requested, issue a new request starting at the first page not returned. Only if that new request reads zero pages (or returns an error)
can you be sure that the page was not dumped.
AUTHOR
was developed by HP.
SEE ALSO
cr_open(3), libcrash(5).
cr_read(3)