search

flatpak / xdg-dbus-proxy

GNU Lesser General Public License v2.1
57 stars 21 forks source link

flatpak-proxy: Tell where "Invalid message header format" comes from #49

Closed hadess closed 1 year ago

hadess commented 1 year ago

Invalid message header format was printed without more details. Printing where the invalid message header came from might help in debugging.

hadess commented 1 year ago

I need to add more error reporting to parse_header() it seems.

hadess commented 1 year ago

Finally something usable :)

** (process:1029439): WARNING **: 10:44:02.354: Invalid message header format from client: Could not parse path in path field
hadess commented 1 year ago

Now that's what I call useful debug:

** (process:1032866): WARNING **: 11:02:58.751: Invalid message header format from client: Could not parse path in path field: String is not nul-terminated (/com/intel/dLeynaServer/server/uuid_3ae3dcaa3c_2d5e83_2d39ed_2dcbd5_2dd6e8863f538b/302f312f446973717565206475)