Fixing a buffer copy issue in DesktopFrame

This CL fixes a buffer copying issue introduced in this CL:
https://webrtc-review.googlesource.com/c/src/+/196485

In the BasicDesktopFrame::CopyOf function, the src and dst params
were swapped.  For me this manifested as a missing cursor when using
Chrome Remote Desktop.  I don't know of any other bugs this caused
but I have to assume it affects all callers of the function given
that the copy will never occur.

Bug: chromium:1197210
Change-Id: I076bffbad1d658b1c6f4b0dffea17d339c867bef
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/214840
Commit-Queue: Joe Downing <joedow@google.com>
Commit-Queue: Jamie Walch <jamiewalch@chromium.org>
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#33672}
1 file changed
tree: 3b5a72fd38973953645196318b185f6dfb3021c7
  1. .clang-format
  2. .git-blame-ignore-revs
  3. .gitignore
  4. .gn
  5. .vpython
  6. AUTHORS
  7. BUILD.gn
  8. CODE_OF_CONDUCT.md
  9. DEPS
  10. DIR_METADATA
  11. ENG_REVIEW_OWNERS
  12. LICENSE
  13. OWNERS
  14. PATENTS
  15. PRESUBMIT.py
  16. README.chromium
  17. README.md
  18. WATCHLISTS
  19. abseil-in-webrtc.md
  20. api/
  21. audio/
  22. build_overrides/
  23. call/
  24. codereview.settings
  25. common_audio/
  26. common_video/
  27. data/
  28. docs/
  29. examples/
  30. g3doc.lua
  31. g3doc/
  32. license_template.txt
  33. logging/
  34. media/
  35. modules/
  36. native-api.md
  37. net/
  38. p2p/
  39. pc/
  40. presubmit_test.py
  41. presubmit_test_mocks.py
  42. pylintrc
  43. resources/
  44. rtc_base/
  45. rtc_tools/
  46. sdk/
  47. stats/
  48. style-guide.md
  49. style-guide/
  50. system_wrappers/
  51. test/
  52. tools_webrtc/
  53. video/
  54. webrtc.gni
  55. webrtc_lib_link_test.cc
  56. whitespace.txt
README.md

WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.

Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.

The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.

Development

See here for instructions on how to get started developing with the native code.

Authoritative list of directories that contain the native API header files.

More info