|
|
Sponsored Content
Operating Systems
Linux
Strange problem with gettimeoftheday function
Post 302184252 by xyz123456 on Friday 11th of April 2008 03:40:27 AM
04-11-2008
Strange problem with gettimeoftheday function
Hi all,
I am using pthread_cond_timedwait function in my program, to generate the time period of waiting i use gettimeoftheday function.
When i run the code after compiling i get a core dump error. However my program runs perfectly if i give a printf statement before the gettimeoftheday function.
Can anyone explain this problem . I have pasted the part of the code for your reference:
pthread_mutex_lock(&lock);
//printf("After core dump \n");
gettimeofday(&tp, NULL);
ts.tv_sec = tp.tv_sec;
ts.tv_nsec = tp.tv_usec * 1000;
ts.tv_sec += WAIT_TIME_SECONDS;
pthread_cond_timedwait(&write, &lock, &ts);
pthread_mutex_unlock(&lock);
Thanks in advance,
I am using pthread_cond_timedwait function in my program, to generate the time period of waiting i use gettimeoftheday function.
When i run the code after compiling i get a core dump error. However my program runs perfectly if i give a printf statement before the gettimeoftheday function.
Can anyone explain this problem . I have pasted the part of the code for your reference:pthread_mutex_lock(&lock);
//printf("After core dump \n");
gettimeofday(&tp, NULL);
ts.tv_sec = tp.tv_sec;
ts.tv_nsec = tp.tv_usec * 1000;
ts.tv_sec += WAIT_TIME_SECONDS;
pthread_cond_timedwait(&write, &lock, &ts);
pthread_mutex_unlock(&lock);
Thanks in advance,
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I¡¯m a network operator, mine is an IBM PC server 320, operating system SCO unix 3.2v4.2, triton 3.1 of Baan. Recently, my server went dead every a few hours, no sign & signal shows malfunction suddenly. It looks like a sudden power failure, but the indicator of main power supply is on. Normal... (1 Reply)
Discussion started by: lyhsm
1 Replies
2. Shell Programming and Scripting
I am using SunOS 5.9 and I don't know why all my commands are getting executed as if an extra 'enter' has been pressed.
What could be the reason and how to correct it?
Please help.
Asty (2 Replies)
Discussion started by: Asty
2 Replies
3. UNIX for Dummies Questions & Answers
Hi ..
is there a way i can retrieve the output of gettimeoftheday in a string (1 Reply)
Discussion started by: p_aishwarya
1 Replies
4. Shell Programming and Scripting
Here is the script:
#!/bin/bash
#set -xv
RAWDATAFILE="temp1"
GOODDATAFILE="temp2"
FindSOS()
{
local NUM=0 #return value for the id of SOS
local cnt=1
if grep "EOS" $1
then
sed -e 's/.*<CobDate>//' -e 's/<\/.*//' <$1 > ${RAWDATAFILE}
sed -n -e '/EOS/,/SOS/ s/*/&/p' <${RAWDATAFILE}... (2 Replies)
Discussion started by: tpltp
2 Replies
5. Shell Programming and Scripting
Well, my script started off to do what i wanted. Now, i think its not recognizing the pattern so its not moving anything.
What i have to do is execute my script command for the move to take effect. So i did that and yayy it worked.
Strange thing is that my DESTDIR was empty to begin with.... (2 Replies)
Discussion started by: oxoxo
2 Replies
6. UNIX and Linux Applications
Segregated the problematic portion, and showing for your view here.,
1. Following is the function definition,
create or replace function new_del(id integer) returns void as $$
begin
raise info 'dollar :%',$1;
delete from testing where id=$1;
end ;
$$
language 'plpgsql';
... (1 Reply)
Discussion started by: thegeek
1 Replies
7. Shell Programming and Scripting
Hi All,
I am encountering an unexpected problem while running my process, using daemon placed in /etc/init.d/.
I have a process that is opening shared library using dlopen.
When I run my process on the command line, it is able to open the library. But when I used daemon to run my process, I... (0 Replies)
Discussion started by: qwerty-1
0 Replies
8. Shell Programming and Scripting
hello all,
i am having problem in accessing a directory.I dont think its a permission issue.can anyone help me out. I am using korn sell
code:
$ ls -ltr sc*
lrwxrwxrwx 1 essbase essbase 21 Oct 8 2010 sc_ssp -> /work/nfs/nas2/sc_ssp
$ cd sc_ssp
ksh: sc_ssp: not found
$ (6 Replies)
Discussion started by: manid
6 Replies
9. Shell Programming and Scripting
I am converting shell script to Perl. In shell I have a code
parse_prog_args()
{
if
then
while
do
case $1 in
-P* | -p* )
export PROCESS_DATE=$2
export MM=`echo $2 | cut -c5-6`
export DD=`echo $2 | cut -c7-8`
export YY=`echo $2 | cut -c3-4`
export... (4 Replies)
Discussion started by: digioleg54
4 Replies
10. Shell Programming and Scripting
In one of my shell function I found the following
set_default_values () {
prog=$1
PROC_DT=$2
RESET_ALL="${3-N}"
#echo "Processing date as passed = , Program name = "
......
I understand the first and second arguments, but don't understand... (1 Reply)
Discussion started by: digioleg54
1 Replies
LEARN ABOUT FREEBSD
crashinfo
CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8) NAME
crashinfo -- analyze a core dump of the operating system SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core] DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX. By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel file can also be explicitly provided via the kernel argument. Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8), ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8). The options are as follows: -d crashdir Specify an alternate core dump directory. The default crash dump directory is /var/crash. -n dumpnr Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory. -k kernel Specify an explicit kernel file. SEE ALSO
textdump(4), savecore(8) HISTORY
The crashinfo utility appeared in FreeBSD 6.4. BSD
June 28, 2008 BSD