I'm a programmer by day and WoW player by... Well, day and night, as I freelance my work :).
I've recently started getting into writing WoW addons and grabbed a copy of "Beginning Lua with World of Warcraft" by the guy who wrote DBM - really good read so far!
I'm at them moment attempting to enable XML debugging with the following command ingame:
/run FrameXML_Debug(1)
After reloading the interface, WoW crashes with a fatal exception:
0xC0000005 (ACCESS_VIOLATION) at 001B:00413DDB
The instruction at "0x00413DDB" referenced memory at "0x00000008".
The memory could not be "read".
I don't often code in higher level languages, so I don't really "get" memory errors :P. Any ideas?
@egingell, FrameXML_Debug(flag) is a built-in API, so I'm not sure that some XML code that doesn't cause the client to crash without it would make it crash with.
@egingell, FrameXML_Debug(flag) is a built-in API, so I'm not sure that some XML code that doesn't cause the client to crash without it would make it crash with.
However, does the stock UI crash too ?
I doubt the stock UI would crash just from calling that function. And I know it's [the function] built-in.
Edit: Yikes, a major patch.
Edit again: The same thing happened to me with no addons loaded.
I'm a programmer by day and WoW player by... Well, day and night, as I freelance my work :).
I've recently started getting into writing WoW addons and grabbed a copy of "Beginning Lua with World of Warcraft" by the guy who wrote DBM - really good read so far!
I'm at them moment attempting to enable XML debugging with the following command ingame:
/run FrameXML_Debug(1)
After reloading the interface, WoW crashes with a fatal exception:
I don't often code in higher level languages, so I don't really "get" memory errors :P. Any ideas?
Cheers!
- nfsnobody
However, does the stock UI crash too ?
I doubt the stock UI would crash just from calling that function. And I know it's [the function] built-in.
Edit: Yikes, a major patch.
Edit again: The same thing happened to me with no addons loaded.