EuGig
EuGig
`1637 pgagroal_log_debug("Header: %s\n", header);` could be the cause of the segmentation fault, since `header` has also `type` and `slot` which are not strings. Oh yeah, calling `write_header_info` inside `read-header` can...
> I've digged anymore to understand why, but it's not clear to me why you are writing the header in different positions. The problem is that `write_header` writes at the...
> No, there is some confusion originating from me: write_header already calls write_header_info, which is what I would expect. I don't get why you should call it also from read_header....
> In other words, the write_info_header function is inserting something in the header when the pgagroal-cli requests a command, but not when pgagroal is answering. As a matter of fact,...
> You could look into expanding the pgagroal_append() infrastructure and use that as the base Thank you for the suggestion @jesperpedersen! I actually used offsets instead. > @EuGig did you...
Just rebased after `5dcfb897d90b78c622a38855ae6ffd5cb2630d9f` fixing [#407].
Thanks, will do!
Hi @fluca1978! > but we already have pgagroal_json_create_new_command_object that accepts the executable name, so I think it would be better to extend such prototype to include also the application version,...
Oh I see! Sounds good.
Oh sorry, I fixed this error. Though, I wonder why my compiler didn't see this.