DC++

Creating bug report for frozen DC++

Asked by Siddhant Saraf

I'm trying to follow the instruction given in https://answers.launchpad.net/dcplusplus/+faq/1865 to create a bug report for frozen DC++, version 0.811.

I have a somewhat dumb question:

When am I actualy supposed to start DC++ ?
Am I supposed to launch DC++ (the normal way), and then _wait_ for it to become frozen and only then start the whole process of finding <thread id>, opening "cmd" and using gdb and so on ? Right ?

I'm just a bit confused.
Thanks,
Sid

Question information

Language:
English Edit question
Status:
Solved
For:
DC++ Edit question
Assignee:
No assignee Edit question
Solved by:
eMTee
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
eMTee (realprogger) said : 		#1

Yes, that's correct.

Revision history for this message
Siddhant Saraf (siddhantsaraf) said : 		#2

Thanks eMTee, that solved my question.

Revision history for this message
Siddhant Saraf (siddhantsaraf) said : 		#3

So I achieved a frozen DC++ ( http://i.imgur.com/fZMYcrT.png ). But when I go to SysInternals, none of the threads have 100% CPU usage. In fact, all threads have no CPU usage (http://i.imgur.com/yybQoVe.png) . Anyhow being unable to identify the bugged thread, I went ahead and attached gdb to thread with id _9156_ because it had that weird Start Address "...!TpCalbackIndependent...". And obtained a stacktrace (http://sprunge.us/VLSW).

Was this process correct? Next time I encounter such a problem, how can improve the collected information for a bug report? (Note- I'm not filing a bug report yet because I'm not even sure if I have the correct inormation for it yet.)

Symptom: DC++ stops working after a random time. Sometimes just a few minutes after start, or sometimes many hours.
Details: DC++, version 0.811, Windows 7, 64-bit

Revision history for this message
eMTee (realprogger) said : 		#4

It doesn't seem to be useful, in these cases it's better to get all the threads' trace the way as it described in the bottom of the FAQ.

Revision history for this message
Siddhant Saraf (siddhantsaraf) said : 		#5

Ok, so here is trace for all the threads: http://sprunge.us/YTjK
And the corresponding Process Explorer - Sysinternals screenshot: http://sprunge.us/YTjK

Is this helpful ?
Do I have enough information to create a bug report ?

Revision history for this message
Siddhant Saraf (siddhantsaraf) said : 		#6

Oops. Here is the correct link for ProcessExplorer: http://i.imgur.com/CKoPihz.png

Revision history for this message
Best eMTee (realprogger) said : 		#7

Not really but since the issue is still there we have to have one. At least you seem to get the problem sooner than others so we can go on with that...
Converted to a bug report.

Revision history for this message
Siddhant Saraf (siddhantsaraf) said : 		#8

Thanks eMTee, that solved my question.