A question about bugs

**neobrain** · 12-31-2012, 09:36 PM **#11**

(12-31-2012, 02:23 PM)Dangeresque Wrote: The only problem is that the bug received little attention at the time

Just because no one answered doesn't mean it got no attention.

(12-31-2012, 02:23 PM)Dangeresque Wrote: and from the comments I don't think any attempts have been made to fix it.

... There's no reason for me to answer if I have no idea wtf could be causing the issue. That probably affects 90% of the other Dolphin devs, and the remaining 10% don't care about your issue (can't care about everything, you know :p) or got no time. Like delroth suggested, finding out which commit caused a regression greatly improves your chances of getting the issue taken care of at all.

(12-31-2012, 02:23 PM)Dangeresque Wrote: When in the situation I'm in, what should I do? I want to be respectful of the devs, but I fell like the issue will never be fixed if it isn't brought to their attention.

Think about what you can do to minimize the amount of work needed to reproduce your issue. Even better, try to get as much debugging done on your side as possible (again: Find out which commit caused the issue). For crashes, you'll ideally want to provide a proper back trace. Coders have limited time resources, so they won't spend hours of work on your issue with work like that just to find out they can't do anything about your issue.
If you have done all of the above steps, keep waiting. Someone will eventually look at your issue. Or not. That's unfortunate, but it's just the way it goes: Some issues never get fixed, which is something that may have numerous reasons, which I won't go into detail here though.

(12-31-2012, 02:23 PM)Dangeresque Wrote: So should I just wait? Is there a good way of letting the devs know?

Your thread's fine. While it would be annoying to read it for every issue out there, we don't have many people like you asking that kindly :p
We've had lots of idiots coming to our forums some time ago asking about the WWE2 or SMG2 issues to get sorted out. Some of them also had the feeling that for whatever reason we didn't even know about the issue (yeah, one noob asking per day isn't enough) and it was just annoying. Annoying devs isn't a good way to get your issue fixed. You'd think that's kinda obvious :p

Dangeresque · 01-01-2013, 02:29 AM **#12**

Ok, so I ran into a problem: I decided to go all the way back to stable 3.0 to see if the bug was back there too (and it was). Now I want to go back to 2.0 and try and find the revision there that caused the bug, but the oldest revision I can get off the main website/google code is 3.0-749. Is there any way to get older revisions than that?

**pauldacheez** · 01-01-2013, 02:34 AM **#13**

http://dl.dolphin-emu.org/oldbuilds/ Here you go.

Dangeresque · (This post was last modified: 01-01-2013, 02:41 AM by Dangeresque.)

Sweet, thanks.

Alright. So I downloaded version 2.0 and the crash is still there. Is there anything older than that I can try?

**neobrain** · 01-01-2013, 02:50 AM **#15**

SS is also maintaining a build archive, maybe he can post the link to that.. I think it's actually sticked somewhere on our forums, but I don't have any time to look it up right now xD

Dangeresque · (This post was last modified: 01-01-2013, 03:26 AM by Dangeresque.)

I found that build archive, thanks.

Alright I found it. The bug showed up between Dolphin-win-x64-r4801 and Dolphin-win-x64-r4812 (Sorry It wont let me direct link, but they're both on SS's skydrive https://skydrive.live.com/?cid=F76F2C2B2135891B&id=F76F2C2B2135891B!105 ).
The thing is, there was no sd card option in 4801, but there was in 4812. What I think this means is that the original sd card code had the bug or it showed up between 4801 and 4812.
Should I also post this information on the google code page for the bug?
This is getting actually kindov fun Smile