02-04-2016
I've tested and found that memset(d->buf, 100,0); instead of fgets does not crash. It's not the act of setting those 100 bytes that causes the crash, it may be related to the file pointer somehow.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how... (1 Reply)
Discussion started by: Kgatliffe
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. HP-UX
Hi,
First of all, thanks for your help. I have downloaded freeBSD to study unix
I'm here again 'cause my HP-UX 10.x has "broken". It raise this error:
----------------------------------------------------
Diagnostic System warning:
= 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies
4. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
5. Solaris
I installed solaris 5.9 on a machine SunBlade100 512Mo of RAM and 18Go of hard disc, after the installation I have remark that the machine starts again after 10mn with 15 mn of walk, I downloaded and installed the last patchs on the machine but the poblème persists. someone can help me and tell me... (0 Replies)
Discussion started by: toufik
0 Replies
6. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
7. Filesystems, Disks and Memory
Hi, First post. I am not to experienced in the Unix or HP-UX world but I'm learning.
We have some problem with a HP rx4640 server. During boot it states the following:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgchange:... (7 Replies)
Discussion started by: hoff
7 Replies
8. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
9. Solaris
I am supporting a server running Solaris 4.3.The server is not having ddicated system administrator and i am requred to do minor maintenance tasks.l From few days, The server is automatically crashing and i just reboot the server. I also do not see anything in /var/adm/messages that can give an... (1 Reply)
Discussion started by: asalman.qazi
1 Replies
10. SCO
Hi,
I need help, one of our servers is down, and all data in that Server are critical:
The Scenario:
-------------
I have a computer with the next architecture:
architecture=IA32
bus_types=PCI2.10,ISA,PnP1.0
hostname=xxx.xxx.xxx (the real name is hidden)
hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
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)