|
|
I would love your feedback on BeAIM, be it bug reports, feature suggestions, flames, or whatnot. So please, if you have any ideas or bugs to report, tell me about them!
Here are the various ways to get in contact with me. If you are reporti
ng a bug, pleasse read the "Bug Reports" section below before you mail me.
- Email: greg@fifthace.com
- AIM: I am sometimes on AIM. This isn't always reliable currently - debugging sometimes involves lots of signing on and off, and after about the tenth time in an hour OSCAR gets mad at me and won't let me sign back on fo
r another hour or so.
Bug Reports:
I need bug reports from you if you can provide them; I can't possibly run into all the bugs by myself. But when you send them, please include the information below:
- A stack crawl.. This would be extremely helpful to me! It's fairly easy to do; read at the bottom of the page to learn how.
- Your BeAIM version. This is very important... lots of people have forgotten so far! If you are running an old version and you don't tell me that, you might send me chasing after bugs that have already been fixed.
- What the problem is. You may think this is common sense, but I have already gotten a few reports saying something to the effect of, "BeAIM doesn't work." I can't really do much with that kind of description... I need to know exactly what
doesn't work!
- Exactly what you did to make the problem happen. I need to know in as much detail as possible what went wrong and how it happened. Please try and see if you can reproduce the problem if you can; bugs that I can reproduce are much easier to fix!
If you can tell me that BeAIM turns your desktop purple on every fifth message you receive from a guy named Odo, then it really helps me track down exactly what is happening.
- If applicable, what kind of client the other person is using. If you are having problems chatting with one specific user, see if you can tell me what kind of AIM client that other person is using. This will help me track down problems that BeAI
M has with, say, the AIM client on the Mac.
- How major the problem is. This kind of varies from person to person, but it would be useful information for me. If it's a bug that won't let you log on, it will be more important for me to fix than if it had been just a cosmetic problem or a ty
po or something. If there is something that seriously prevents you from using BeAIM, I will try to get it fixed for you ASAP.
How to do a Stack Crawl
or, How to make Greg Eternally Grateful
OK, say BeAIM has crashed (which it tends to do on occasion). It throws a message onscreen saying something about a "segment fault" and maybe a little technical information. There are two buttons: "OK," which kills the application, and "Details," which gi
ves you more information. Press "Details."
You get another message, which has two more buttons: "OK," which also kills the app, and "Debug." Press the "Debug" button, and a terminal window opens with some scary looking stuff in it that will make no sense to you unless you're a programmer-type.
On the screen, there is a text prompt waiting for you to type something. Type these two letters: sc
and hit Enter.
That stands for Stack Crawl, but you don't need to know that. Typing sc gives you a few more lines of gobbledy-gook... anywhere from 1 line to 20 or 30. Copy all the stuff from the terminal, and paste it into StyledEdit (or your email client, or a
nywhere you can paste). Then, send that to me (via email, please) and it will make debugging much easier for me! I would really appreciate it if you could do this when BeAIM crashes.
Just a side note: sometimes, when you do a stack crawl, you may get one line that repeats itself over and over and over. If that happens, you only need to send me one line of it... I don't need 300 lines that are all the same. Thanks. :-)
|