|
Bugzilla – Full Text Bug Listing |
| Summary: | DCCP example crashed | ||
|---|---|---|---|
| Product: | dce | Reporter: | Hajime Tazaki <tazaki> |
| Component: | other | Assignee: | Hajime Tazaki <tazaki> |
| Status: | CONFIRMED --- | ||
| Severity: | major | CC: | ns-bugs |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Hajime Tazaki
2012-11-19 20:09:42 UTC
In ucontext fiber, there is no such a problem. a task (dccp client app) is scheduled after exit of the process, then wakeup function points freed area of the memory. wakeup is called from the kernel (i.e., scheduled_timeout), but no idea how to cancel it when exit (), and don't understand why ucontext is okay. I guess this is not DCCP-specific problem. |