(hoping this does not generate a firestorm)
If you are writing code that gets called from IPC_MESSAGE_HANDLER, in
other words you are writing or reviewing an IPC message handler,
please:
1- Consider the possibility of receiving a bad message (i.e a message
whose payload does not make sense, or is inconsistent)
2- When handling a bad message don't silently ignore it.
3- When handling a bad message from another process, the most sane
path of action (when possible) is to call
process()->ReceivedBadMessage();
This is strongly recommended if you are handling messages coming from
a renderer.
ReceivedBadMessage() current behavior is to terminate the offending
renderer (call BadMessageTerminateProcess())
BadMessageTerminateProcess() has DCHECK()s and LOG() stuff so if you
are calling ReceivedBadMessage() do not put them in your code.
-cpu
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
