| Summary: | [abrt] pptp-1.7.2-12.fc15: __GI_raise: Process /usr/sbin/pptp was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> | ||||||
| Component: | pptp | Assignee: | Jaroslav Škarvada <jskarvad> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 18 | CC: | jskala, navid.htb, paul, sheepdestroyer, spetreolle | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:9908c32a8a84f5ba7403da2627da5b9e30ca7a80 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-02-05 22:44:17 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Mads Kiilerich
2012-01-05 16:06:07 UTC
Created attachment 550955 [details]
File: var_log_messages
Created attachment 550956 [details]
File: backtrace
Running pppd through valgrind I get ==3477== Warning: invalid file descriptor -1 in syscall close() ==3477== at 0x5F8D670: __close_nocancel (syscall-template.S:82) ==3477== by 0x11DC1A: safe_fork (in /usr/sbin/tmp/pppd) ==3477== by 0x11DF9B: device_script (in /usr/sbin/tmp/pppd) ==3477== by 0x13B839: connect_tty (in /usr/sbin/tmp/pppd) ==3477== by 0x12C8DA: start_link (in /usr/sbin/tmp/pppd) ==3477== by 0x11C284: main (in /usr/sbin/tmp/pppd) It is very likely that the connection (and thus stdin/stdout) is closed at an unfortunate moment. This valgrind error doesn't look serious, but perhaps it hits something more dangerous when the timing is unfortunate. FWIW, the pptp launched by pppd warns ==3486== Invalid read of size 4 ==3486== at 0x4080DB: call_callback (pptp_callmgr.c:83) ==3486== by 0x404044: pptp_call_destroy (pptp_ctrl.c:412) ==3486== by 0x4040FB: pptp_conn_destroy (pptp_ctrl.c:449) ==3486== by 0x408D13: callmgr_main (pptp_callmgr.c:297) ==3486== by 0x402817: launch_callmgr (pptp.c:505) ==3486== by 0x402971: open_callmgr (pptp.c:474) ==3486== by 0x401E98: main (pptp.c:375) ==3486== Address 0x53f4f10 is 0 bytes inside a block of size 12 free'd ==3486== at 0x4C2962E: free (vg_replace_malloc.c:366) ==3486== by 0x408E55: callmgr_main (pptp_callmgr.c:238) ==3486== by 0x402817: launch_callmgr (pptp.c:505) ==3486== by 0x402971: open_callmgr (pptp.c:474) ==3486== by 0x401E98: main (pptp.c:375) Can you repeat this with pptp-1.7.2-14.fc15 (just pushed to updates-testing)? I can't reproduce the crash on demand, neither with the old nor the new version. I get the same (slightly changed) valgrind warning with pptp-1.7.2-14.fc16.x86_64: ==3814== Invalid read of size 4 ==3814== at 0x4082CB: call_callback (pptp_callmgr.c:85) ==3814== by 0x404254: pptp_call_destroy (pptp_ctrl.c:412) ==3814== by 0x40430B: pptp_conn_destroy (pptp_ctrl.c:449) ==3814== by 0x409023: callmgr_main (pptp_callmgr.c:304) ==3814== by 0x402917: launch_callmgr (pptp.c:527) ==3814== by 0x402A71: open_callmgr (pptp.c:496) ==3814== by 0x401F68: main (pptp.c:394) ==3814== Address 0x53f4f10 is 0 bytes inside a block of size 12 free'd ==3814== at 0x4C2962E: free (vg_replace_malloc.c:366) ==3814== by 0x409174: callmgr_main (pptp_callmgr.c:245) ==3814== by 0x402917: launch_callmgr (pptp.c:527) ==3814== by 0x402A71: open_callmgr (pptp.c:496) ==3814== by 0x401F68: main (pptp.c:394) Thanks - I've reported this upstream: http://marc.info/?l=pptpclient-devel&m=132586093126446&w=2 Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. got this problem on fedora 18 Got it again on F18, please reopen Are you able to get a backtrace? abrt-gui went directly to "problem already reported" where i got the link to this bug. But now the problem doesn't appear in the "not submitted reports" list nor the "submitted reports" list, even if selecting "show all problems". I had at least two occurrences of it. How to get them back and do the backtrace? (In reply to comment #12) > abrt-gui went directly to "problem already reported" where i got the link to > this bug. > > But now the problem doesn't appear in the "not submitted reports" list nor > the "submitted reports" list, even if selecting "show all problems". > I had at least two occurrences of it. How to get them back and do the > backtrace? Don't know I'm afraid. The original backtrace dates back to F-16 and I'd really prefer to see a current one. Perhaps you'll have to wait until it happens again? This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |