| Anonymous | Login | Signup for a new account | 2024-04-16 21:55 CEST | |
| My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0000594 | aMule | External Conn | public | 2005-10-05 21:38 | 2008-03-24 13:53 | ||||
| Reporter | nich | ||||||||
| Assigned To | Xaignar | ||||||||
| Priority | normal | Severity | crash | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | SVN | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000594: amulecmd locks on "servers" command | ||||||||
| Description | When connecting to a localhost amuled the "servers" command causes amulecmd to stop (apparently waiting for some response packet). When connecting amulecmdDLG to the same localhost amuled, the "servers" command is ignored once. In the second time it triggers a wxGTK Debug Alert window. | ||||||||
| Additional Information | The uploaded file contains the amulecmdDLG bt after the debug window has been triggered and an amulecmd bt after stoping it with ^C. | ||||||||
| Tags | No tags attached. | ||||||||
| Fixed in Revision | |||||||||
| Operating System | |||||||||
| Attached Files |  amulecmd.bts.log [^] (31,612 bytes) 2005-10-05 21:38 | ||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0001316) GonoszTopi (administrator) 2005-10-15 00:21 |
In both cases wx is waiting data from the socket. In the DLG version, the assert is caused by wxYield() called recursively/twice. In the command-line version, it is waiting for data that (I think) will never arrive. I guess the same happens with the gui version, but you don't see it waiting. The interesting part of the backtrace: 0000014 0x0805fea2 in CECTag::ReadChildren (this=0x80fcab0, socket=@0x80ca688) at ECPacket.cpp:509 i = 5247 tmp_tagCount = 5558 Do you really have 5558 servers in your server list? I think that the packet got corrupted. Unfortunately we don't have anything to detect/recover corruption in the protocol data. At least I should build a tool to investigate/debug EC protocol. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2005-10-05 21:38 | nich | New Issue | |
| 2005-10-05 21:38 | nich | File Added: amulecmd.bts.log | |
| 2005-10-15 00:21 | GonoszTopi | Note Added: 0001316 | |
| 2008-03-24 13:53 | Xaignar | Status | new => resolved |
| 2008-03-24 13:53 | Xaignar | Resolution | open => fixed |
| 2008-03-24 13:53 | Xaignar | Assigned To | => Xaignar |
|
Issue History |
| Copyright © 2000 - 2024 MantisBT Team |
 |