So I've tested it on a OpenSuse machine. And there it behaves a little bit different. Instead of finishing there will be raised a segmentation fault. Here is the sample output for UPPER_BOUND = 500000000 and 500 ms intveral:
Ubuntu and VMWare:
What could be the reason of this segmentation fault. Could it be raised because of some mistakes in initializing the alternative signal stack? Does anyone has a good source, which explains, what happens inside the OS, when a context is swapped or a signal is raised? I didn't find anything on the web... :/
HI,
I need to handle SIGUSR2 signal in my application to change the state of the application dynamically. I have implemented the signal handler. However the application is able to catch only one SIGUSR2 signal. The second SIGUSR2 signal causes the application to crash. This is happning only with... (3 Replies)
Hi folks
I'm trying to write a signal handler (in c on HPUX) that will catch the child process launched by execl when it's finished so that I can check a compliance file.
The signal handler appears to catch the child process terminating however when the signal handler completes the parent... (3 Replies)
Guys,
I'm doing signal handling in Perl. I'm trying to catch ^C signal inside the script.
There two scripts : one shell script and one perl script.
The shell script calls the perl script.
For e.g. shell script a.sh and perl scipt sig.pl.
Shell script a.sh looks something like this :... (6 Replies)
#1: does anyone know how to detect how many times (and/or the time length) a given thread has been context switched out of the CPU?
#2: are there any tchniques that minimize/eliminate your thread getting context switched?
I would be happy to know the answers to these questions for ANY... (2 Replies)
Hello all,
I am starting to learn signal handling in Linux and have been trying out some simple codes to deal with SIGALRM. The code shown below sets a timer to count down. When the timer is finished a SIGALRM is produced. The handler for the signal just increments a variable called count. This... (7 Replies)
I am trying to write a small program where I can send signals and then ask for an action to be triggered if that signal is received. For example, here is an example where I am trying to write a programme that will say you pressed ctrl*c when someone presses ctrl+c. My questions are what you would... (1 Reply)
i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.
my code is
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
j=(char *)malloc(10);
... (4 Replies)
hi friends i have a problem in signal handling ...
let me explain my problem clearly..
i have four process ..
main process forks two child process and each child process again forks another new process respectively...
the problem is whenever i kill the child process it is reforking and the... (2 Replies)
Discussion started by: senvenugopal
2 Replies
LEARN ABOUT DEBIAN
bio::tools::eutilities::link::urllink
Bio::Tools::EUtilities::Link::UrlLink(3pm) User Contributed Perl Documentation Bio::Tools::EUtilities::Link::UrlLink(3pm)NAME
Bio::Tools::EUtilities::Link::UrlLink - class for EUtils UrlLinks
SYNOPSIS
# ...
DESCRIPTION
# ...
FEEDBACK
Mailing Lists
User feedback is an integral part of the evolution of this and other Bioperl modules. Send your comments and suggestions preferably to one
of the Bioperl mailing lists. Your participation is much appreciated.
bioperl-l@lists.open-bio.org - General discussion
http://www.bioperl.org/wiki/Mailing_lists - About the mailing lists
Support
Please direct usage questions or support issues to the mailing list:
bioperl-l@bioperl.org
rather than to the module maintainer directly. Many experienced and reponsive experts will be able look at the problem and quickly address
it. Please include a thorough description of the problem with code and data examples if at all possible.
Reporting Bugs
Report bugs to the Bioperl bug tracking system to help us keep track the bugs and their resolution. Bug reports can be submitted via the
web.
https://redmine.open-bio.org/projects/bioperl/
AUTHOR
Email cjfields at bioperl dot org
APPENDIX
The rest of the documentation details each of the object methods. Internal methods are usually preceded with a _
get_dbfrom
Title : get_dbfrom
Usage :
Function :
Returns :
Args :
get_attribute
Title : get_attribute
Usage :
Function :
Returns :
Args :
get_icon_url
Title : get_icon_url
Usage :
Function :
Returns :
Args :
get_subject_type
Title :
Usage :
Function :
Returns :
Args :
get_url
Title : get_url
Usage :
Function :
Returns :
Args :
get_link_name
Title : get_link_name
Usage :
Function :
Returns :
Args :
get_provider_name
Title : get_provider_name
Usage :
Function :
Returns :
Args :
get_provider_abbr
Title : get_provider_abbr
Usage :
Function :
Returns :
Args :
get_provider_id
Title : get_provider_id
Usage :
Function :
Returns :
Args :
get_provider_icon_url
Title : get_provider_icon_url
Usage :
Function :
Returns :
Args :
get_provider_url
Title : get_provider_url
Usage :
Function :
Returns :
Args :
to_string
Title : to_string
Usage : $foo->to_string()
Function : converts current object to string
Returns : none
Args : (optional) simple data for text formatting
Note : Used generally for debugging and for various print methods
perl v5.14.2 2012-03-02 Bio::Tools::EUtilities::Link::UrlLink(3pm)