Bug 558164 - [abrt] crash in perl-4:5.10.0-87.fc12
Summary: [abrt] crash in perl-4:5.10.0-87.fc12
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: perl
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:89526da2c9ef0499ea791d05b67...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-24 02:16 UTC by Senthil
Modified: 2010-01-27 10:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-27 10:03:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (4.06 KB, text/plain)
2010-01-24 02:16 UTC, Senthil
no flags Details

Description Senthil 2010-01-24 02:16:06 UTC
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. Exit the parent process with POSIX::exit
2. Fork the process in infinite loop  


Comment: Trying to create a daemon process
Attached file: backtrace
cmdline: /usr/bin/perl -w ./start -mGoal -i0 -ls -n 1
component: perl
executable: /usr/bin/perl
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: perl-4:5.10.0-87.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Senthil 2010-01-24 02:16:10 UTC
Created attachment 386399 [details]
File: backtrace

Comment 2 Marcela Mašláňová 2010-01-26 14:23:37 UTC
Please attach a minimalistic script which could reproduce this behaviour.

Comment 3 Senthil 2010-01-27 09:40:11 UTC
I am not able to reproduce this bug.

Anyways following is the piece of code which i was trying to execute.

I faced the issue when i reduced the sleep by 2 seconds in allowLogin subroutine which hits mysql db.

SCHEDULER: {
    
unless ( $id = fork ) {
   &retryLogin();
   redo SCHEDULER;
} else {
   &allowLogin($n, $p);
  POSIX::_exit( 0 );  
 }
}

Comment 4 Marcela Mašláňová 2010-01-27 10:03:47 UTC
I'm sorry but without short script is can't reproduce for me. I can't say if it's problem somewhere in your code or in the intepreter.


Note You need to log in before you can comment on or make changes to this bug.