Skip to content

Pointed me to the wrong addon #159

@Kidster3001

Description

@Kidster3001

Describe the problem

Bugsack reported an error while calling C_Item.GetItemInfo() with a valid argument. It was telling me the file and line number in Addon 'X'. I eventually traced the problem to another addon 'Y' that was calling the same function with a nil argument.
Wiping Previous bugs on every session will prevent this problem, but that is something I rarely do.

Did this happen on PTR/Beta or the live version of WoW?

Live. 12.0.0

What steps will reproduce the problem?

  1. Have an addon call C_Item.GetItemInfo(nil) or use /run to create the error and an entry in Bugsack.
  2. ReloadUI to get a new Bugsack session. Not necessary but useful for this demonstration.
  3. Have a different addon call the same function with a nil arg.
  4. You will see the error from step 1 reported in Bugsack 'Current session'
  5. Wipe Previous bugs, reverse the addons/commands used in steps 1 & 3.
  6. The error reported by Bugsack 'Current session' is always the error caused by step 1..

Attach a screenshot below to help describe your issue (Attach directly, do not link to other websites)

n/a

What version of the addon are you using? (Stating 'latest' is not useful)

Bugsack 11.2.9
BugGrabber 11.2.7

Do you have an error log of what happened?

n/a

Any additional information? (example: WoW language if not English)

none

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions