Edit - Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

sadly for many of them it's just a number/offset/address that can be a valid value for many of the entries. For example: I must confirm that item #11 of a crash event is always the method offset. Otherwise I can't use that number. If it's not well defined then the data is pretty useless so it seems likely that it IS indeed well defined. But potentially it could be well defined for specific versions of windows or specific circumstances (e.g a .NET app crashing vs a different app). That's the documentation I need.
– Anders Forsgren
Commented Nov 24, 2023 at 7:57
Unfortunately this documentation does not exist, at least publicly. Microsoft does not document areas for which it prefers to be free to change without notice. You will need to change your search to something that's perhaps similar to what I have outlined.
– harrymc
Commented Nov 24, 2023 at 9:54
There is no way of telling a method address from a method offset because they are both just numbers. If it's truly "this is subject to change" or "this order should not be relied on" etc. then perhaps that fact might be documented somewhere? Otherwise the answer could be either this "this isn't documented, and not even the fact that it isn't documented isn't documented" is the answer to my question.
– Anders Forsgren
Commented Nov 24, 2023 at 9:59
I'm trying to find you a method that works, rather than giving a negative answer.
– harrymc
Commented Nov 24, 2023 at 11:05
Thanks. The problem is solved. I have all the suggestions implemented (match value when possible, use index when impossible and so on) But it could be brittle. Or it could be future proof. I don't know. The question now is basically "what will make this break?"
– Anders Forsgren
Commented Nov 24, 2023 at 14:36

| Show 2 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »