Closed
Bug 1054632
Opened 10 years ago
Closed 10 years ago
constructor init list in wrong order in CrashGenerationServer
Categories
(Toolkit :: Crash Reporting, defect)
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: longsonr, Assigned: longsonr)
References
Details
Attachments
(1 file)
1.18 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8474084 -
Flags: review?(ted)
Updated•10 years ago
|
Summary: constructor arguments in wrong order in CrashGenerationServer → constructor init list in wrong order in CrashGenerationServer
Comment 2•10 years ago
|
||
Per bug 666646 comment 3 / bug 666646 comment 4, this is code from upstream, and we should perhaps fix this upstream or else the warning will be reintroduced the next time we update the breakpad library.
(Looks like this code is the same upstream as in our tree, so this hasn't already been fixed upstream:
dump_callback_ listed before filter / filter_context in init list:
https://code.google.com/p/google-breakpad/source/browse/trunk/src/client/mac/crash_generation/crash_generation_server.cc#40
...but after them in class definition:
https://code.google.com/p/google-breakpad/source/browse/trunk/src/client/mac/crash_generation/crash_generation_server.h#121
)
Updated•10 years ago
|
Component: XPCOM → Breakpad Integration
Product: Core → Toolkit
Version: unspecified → Trunk
Comment 3•10 years ago
|
||
Comment on attachment 8474084 [details] [diff] [review]
patch
Review of attachment 8474084 [details] [diff] [review]:
-----------------------------------------------------------------
I can land this upstream. Is this just code hygiene or does it give a compiler warning in newer compilers or what?
Attachment #8474084 -
Flags: review?(ted) → review+
Comment 4•10 years ago
|
||
Landed upstream:
https://code.google.com/p/google-breakpad/source/detail?r=1366
Comment 5•10 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #3)
> I can land this upstream. Is this just code hygiene or does it give a
> compiler warning in newer compilers or what?
It triggers a compiler warning in GCC and clang, for all versions I'm aware of. Thanks for upstreaming it!
Assignee | ||
Updated•10 years ago
|
Flags: in-testsuite-
Assignee | ||
Comment 6•10 years ago
|
||
Comment 7•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•