Closed
Bug 1057402
Opened 11 years ago
Closed 11 years ago
Log the message type when we get a message error
Categories
(Core :: IPC, defect)
Core
IPC
Tracking
()
People
(Reporter: khuey, Assigned: khuey)
References
Details
Attachments
(2 files)
|
5.27 KB,
patch
|
bent.mozilla
:
review+
|
Details | Diff | Splinter Review |
|
2.72 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Attachment #8477442 -
Flags: review?(bent.mozilla)
| Assignee | ||
Comment 1•11 years ago
|
||
Testing with this produces:
158 INFO ###!!! [Parent][DispatchAsyncMessage] Error: (msgtype=5898241,name=???) R
oute error: message sent to unknown actor ID
159 INFO ###!!! [Parent][MessageChannel] Error: Channel error: cannot send/recv
And from msgtype we can back out the protocol and message.
Comment on attachment 8477442 [details] [diff] [review]
Patch
Review of attachment 8477442 [details] [diff] [review]:
-----------------------------------------------------------------
::: ipc/glue/MessageChannel.cpp
@@ +1578,5 @@
> NS_RUNTIMEABORT("unknown Result code");
> return false;
> }
>
> + char printedMsg[256];
How about 512? Some of these protocol/message names can be long
@@ +1579,5 @@
> return false;
> }
>
> + char printedMsg[256];
> + PR_snprintf(printedMsg, 256, "(msgtype=%d,name=%s) %s",
How about this:
PR_snprintf(printedMsg, sizeof(printedMsg),
"(msgtype=0x%lx, name='%s') %s",
aMsg.type(), aMsg.name(), errorMsg);
Important bits are that you don't want to hardcode size twice, and msg.type() returns a 32bit number.
Attachment #8477442 -
Flags: review?(bent.mozilla) → review+
| Assignee | ||
Comment 3•11 years ago
|
||
| Assignee | ||
Comment 4•11 years ago
|
||
status-b2g-v2.0:
--- → fixed
| Assignee | ||
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/1324c90058c2
https://hg.mozilla.org/mozilla-central/rev/c75ac37ffe0d
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
Updated•11 years ago
|
status-b2g-v2.1:
--- → fixed
status-firefox32:
--- → wontfix
status-firefox33:
--- → wontfix
status-firefox34:
--- → fixed
Updated•11 years ago
|
Flags: qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•