| Summary: | segfault in pcscd while removing usb during transaction | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alon Levy <alevy> |
| Component: | pcsc-lite | Assignee: | Bob Relyea <rrelyea> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | dblechte, kalevlember, ppisar, rrelyea |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 13:36:10 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Alon Levy
2011-02-02 16:15:46 UTC
I'm not so sure it is a simple patch. The question here is why is IFDH_get_capabilities zero? It comes from the function pointer in the context: rContext->psFunctions.psFunctions_v2.pvfGetCapabilites It would be good to know what rContext->psFunctions.psFunctions_v2 looked like (actually looking at *rContext would be good as well). bob OK, the .psFunctions_v2.pvfGetCapabilities function is set in reader_factory.c. If the context was initialized, then there is no way that this function could be NULL, We could have failed to initialize the ifd_ handler and logged the "IFDHandler functions missing: GetCapabilities".
That means either 1) the rContext is not initialized properly, or 2) rContext is not really an rContext, or 3) rContext has been trashed by something.
I guess I would like to see the following:
1) start pcscd in the debugger with a break point at RFInitializeReader(). When RFInitializeReader returns print out *rContext. Do this for all calls to RFInitializeReader() (They should all be at the begining).
2) continue running pcsc until you fail. print out *rContext when you fail.
You can run pcscd in the debugger as follows:
As root:
# service pcscd stop
# gdb /usr/sbin/pcscd
gdb> {set break points}
gdb> run -d -f
-d tells pcscd to output lots of debugging info. -f tells pcscd not to daemonize (run in the foreground).
bob
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |