!BugGrabber

I find a automatic mining addon,with 3.3.2 patch
www.RatingBuster.org
I appreciate all the hard work you've put into it.Very simple.

BloOooddemon has spammed the same message over multiple addons. I sense a keylogger.....

Hi!, thank you for the great addon btw. Either this or bugsack is being quirky though. You turn it so that no sound should come up on error capture, but it still goes off like crazy and those noises are well, a little bit annoying. Is that something blizz did to kill your addon or?

I have the r149 version, but WoW is telling me that it's still out of date. Is there a problem with its version listing, or something?

Click the addons button on char select. Top right of new window, turn on load out of date addons.

I cannot run WoW without continuous errors

[2009/07/01 16:21:32-162-x1]: QuestHelper-1.0.25\utility.lua:126: Abort!
QuestHelper-1.0.25\utility.lua:126: in function `Error'
QuestHelper-1.0.25\utility.lua:347: in function `Assert'
QuestHelper-1.0.25\director_quest.lua:392: in function
QuestHelper-1.0.25\director_quest.lua:629: in function `func'
QuestHelper-1.0.25\manager_event.lua:43: in function
QuestHelper-1.0.25\manager_event.lua:58: in function

---


[2009/07/01 16:21:32-162-x1]: QuestHelper-1.0.25\utility.lua:126: Abort!
QuestHelper-1.0.25\utility.lua:126: in function `Error'
QuestHelper-1.0.25\utility.lua:347: in function `Assert'
QuestHelper-1.0.25\tooltip.lua:84: in function `QH_Tooltip_Defer_Add'
QuestHelper-1.0.25\director_quest.lua:381: in function
QuestHelper-1.0.25\director_quest.lua:420: in function
QuestHelper-1.0.25\director_quest.lua:489: in function `QuestProcessor'
QuestHelper-1.0.25\director_quest.lua:687: in function `func'
QuestHelper-1.0.25\manager_event.lua:43: in function
QuestHelper-1.0.25\manager_event.lua:58: in function

that is a quest helper error not this addon

Is there a place to look up errors? I'm posting here because I have no idea where to look, although the problem has probably nothing to do with buggrabber.
I know, the first line should show the offending addon, but it doesn't.
The line is:
Interface\\FrameXML\\UIParent.lua:2477: attempt to compare nil with number:
There is no FrameXML-Addon and no UIParent.lua in my addon folder.
I'm getting this error very frequently (counter=1734 in last session) and during Wintergrasp battle Buggrabber is getting flooded with this error and stops recording it.
I would like to fix the error, because without Buggrabber I wouldn't be able to play at all.
Thanks for your work!

Problem solved. Just in case somebody has a similar situation: I looked up line 2477 in one of the repositories, copied the function which was defined there, and searched all addons for a call of that function (thanks to an advice from WoWAce forums). That way I could identify the culprit.

first off i just want to say you did a good job with this addon. Only thing is it is too good like m game kept crashing and I could not figured out why.but some lucky glitch a error message came through and told I had to update due to me reinstalling the game. The problem was buggrabber and bugsack was grabbing the error before I seen it until the glitch happened now wow runs great. I suggest and error level where if it is very important to see this error then it should still go through to user visibly so that critical errors dont keep us off the game and trying to figure out what is wrong. I even went as far as to removing hardware thinking it was that. But like I said good job. keep it up!

Is there a way to remove the loud "FATALITY" sound?

is there any way to have it let through informational error messages like "you can't do that in combat" or "that water is too shallow to fish" or "Requires Herbalism 400"? not being able to see these is EXTREMELY inhibiting and as nice as this addon is I'm considering dropping it because of this.

This addon does not do anything even remotely related to those kind of errors.

Jeania, delete the MinimapButtonFrame addon. I have worked.

going through the lua, it keeps saying that buggrabber is having errors, if i'm not mistaken in reading it...let me give an example, and you can tell me what it means lol I had a bunnnch of these when I was in a raid group...any explainations?

["message"] = "ADDON_ACTION_BLOCKED:AddOn '!BugGrabber' tried to call the protected function 'RaidGroupButton24:Show()'.\n: in function `Show'\nBlizzard_RaidUI\\Blizzard_RaidUI.lua:505: in function `RaidGroupFrame_Update'\nInterface\\FrameXML\\RaidFrame.lua:81: in function `RaidFrame_Update':\nInterface\\FrameXML\\RaidFrame.lua:61: in function `RaidFrame_OnEvent':\nBlizzard_RaidUI\\Blizzard_RaidUI.lua:154: in function \n\n ---",
["type"] = "event",
["time"] = "2008/10/29 20:21:42",
["session"] = 3,
["counter"] = 15,

Same here.. I have the same problem.

Is there a way to disable the spam that comes up when there's a lot of errors? Having to scroll through the "Buggrabber has started capturing errors" "Buggrabber has stopped capturing errors as it has captured more than 20 errors per second" or whatever it says is kinda annoying in raids :( Are there any slash commands that I'm missing?

Those errors go away when you fix your addons ;) If they're throwing errors, disable them.

That's the thing - It won't actually tell me what addons are causing errors, and all the addons I use that could possibly cause any errors are in working order. Even with bugsack or just the /buggrabber # command, it doesn't give me any useful information. It's not a big problem, it'd just be nice to be able to disable that, or change the message to something smaller.

Go to your SavedVariables folder in the WTF folder and open the !buggrabber.lua file with a text editor. You can then read all the errors captured and turn off the addons that are causing problems.