Skip to content

Commit

Permalink
flatpak-proxy: Tell where "Invalid message header format" comes from
Browse files Browse the repository at this point in the history
"Invalid message header format" was printed without more details.
Printing where the invalid message header came from might help in
debugging.
  • Loading branch information
hadess committed Jul 19, 2023
1 parent d3c1faa commit 052e26a
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions flatpak-proxy.c
Original file line number Diff line number Diff line change
Expand Up @@ -2170,7 +2170,7 @@ got_buffer_from_client (FlatpakProxyClient *client, ProxySide *side, Buffer *buf
header = parse_header (buffer, client->serial_offset, 0, 0);
if (header == NULL)
{
g_warning ("Invalid message header format");
g_warning ("Invalid message header format from client");
side_closed (side);
buffer_unref (buffer);
return;
Expand Down Expand Up @@ -2340,7 +2340,7 @@ got_buffer_from_bus (FlatpakProxyClient *client, ProxySide *side, Buffer *buffer
header = parse_header (buffer, 0, client->serial_offset, client->hello_serial);
if (header == NULL)
{
g_warning ("Invalid message header format");
g_warning ("Invalid message header format from bus");
buffer_unref (buffer);
side_closed (side);
return;
Expand Down

0 comments on commit 052e26a

Please sign in to comment.