[tor-bugs] #18935 [Applications/Tor Browser]: MS bugs - Danger! Windows updates break everything on their way!
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed May 4 19:24:45 UTC 2016
#18935: MS bugs - Danger! Windows updates break everything on their way!
--------------------------------------+---------------------------
Reporter: bugzilla | Owner: tbb-team
Type: defect | Status: closed
Priority: High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Critical | Resolution: duplicate
Keywords: tbb-crash | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+---------------------------
Comment (by gk):
Replying to [comment:16 bugzilla]:
> Huh, of course, you can be sure you've fixed a bug without STR if you
know what you're doing. Just reading the code and understanding the
processes are enough to search, localize and fix the bugs. E.g. see
https://mxr.mozilla.org/mozilla-esr45/source/configure.in#5448. Do you see
that {{{-DPIC}}} is missing? So much time passed, so much testing
passed... Where are the tickets? And what kind should they be? Just
reports of random crashes in non-related tickets, and you've written that
it's your preferred option... OK, if so, please, post here how you can do
things like that, based on this example: how you do search in Bugzilla
(criteria), how you detect that found tickets are caused by -DPIC
underlying problem, and, of course, your STR for this issue! (And who told
you that every bug had STR...)
I think you misunderstood me. I was talking about STR in this context:
crashes on closed source software which oneself cannot reproduce. Even if
I think I have a fix and give it to a user to test she/he needs to have
some steps to say, "Yes, it works" or "No, it does not work".
I closed this ticket as duplicate because this seemed to be mainly about
EMET.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18935#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list