[Bug 10134] regtlib.exe from .NET 1.1's dotnetfx. exe installer crashes with heap problem

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Feb 27 04:06:01 CST 2008


--- Comment #29 from Anastasius Focht <focht at gmx.net>  2008-02-27 04:06:00 ---

@Dmitry Timoshkov  
--- quote ---

> Please do not post disassembled sections of microsoft code for any reason ever.

Even if that's the failing application code and not the OS one?
--- quote ---

Dan Kegel probably considers debugging *any* Microsoft produced code
(installers, apps) potentially hostile/harmful - that far extends the wine
restriction of not touching/looking at OS code.
My snippets are *application* layer snippets - I don't consider .NET Framework
a part of OS.

I mainly post short app traces/assembly/pseudo code snippets for following

- document/show interesting problems to readers
- proof/evidence for people how stuff is accessed to justify my
conclusions/writings/patches/input for patches
- document my own work flow (bugzilla = "notepad") to be archived by
google/mailing lists

People aren't actually believing if I only write prose (good example from
recent times: "the PEB loader lock needs to be exposed").
In fact some .NET patches would never made possible .. not mentioning countless
analysis/patches from previous times.

Anyway if you really take your policy to that extent then you should also
disallow posting/attaching *any* backtraces and crashes from Microsoft related
products (installers, apps) because technically they contain disassembly
(although only a few opcode sequences from crash location).

If you really persist this way then you have lost another supporter.
I won't change my way of documenting bugs/supplying information. Period.


Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the wine-bugs mailing list