New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perl complains and dies on receiving a signal #13111
Comments
From sab123@hotmail.comCreated by sab123@hotmail.comThis is a bug report for perl from sab123@hotmail.com, ----------------------------------------------------------------- I have an application (the module Triceps as available on CPAN) Signal SIGUSR2 received, but no signal handler set. An example of stack in the core file: (gdb) bt (the stack varies between the runs). For all I can tell, the The appearance of the message and of the core dump depends on timing, There are multiple threads that get sent this signal at about the The signal handler is set at the start of the program: $SIG{USR2} = sub {}; There is no race with the thread creation: the killing is enabled And example of a log from such a run: $ PERL_TEST_DIFF='diff -u ' ~/perl519/bin/perl t/xTqlMt.t It looks like there is some issue with initializing the table of the handlers Perl Info
|
From @jkeenanOn Thu, 18 Jul 2013 04:28:05 GMT, sab123@hotmail.com wrote:
Several questions: 1. Do you still experience this problem in the environment where you originally saw it? 2. Does the problem persist with more recent versions of Perl (5.20, 5.22, 5.24)? 3. Would you be able to supply a small program, independent of Triceps, that reproduces the problem? Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#118929 (status was 'open')
Searchable as RT118929$
The text was updated successfully, but these errors were encountered: