[c++] after changing stripped binary to unstripped (with the same Build Id) parca doesn't run symbolizer on it (again) about parca HOT 3 OPEN

Not at the moment, the way our customers prevent this from ever happening, is by uploading the debuginfo in CI/CD before the binary is ever in production using parca-debuginfo. That way they can also run stripped binaries in production.

That said, I think we would be open to improvements here where we not only allow reuploading when existing debuginfo is invalid but also if other debuginfos are better quality (eg. existing debuginfo only includes symtab but not debug_info and the new one does).

from parca.

You’re gonna have to delete it because what probably happened was that your binary had some symbols left so the agent still uploaded something. Now it won’t reupload as “valid” debuginfo has already been uploaded.

It’s located in /debuginfo/<build-id> of your configured object storage provider.

from parca.

That's exactly what happened. Is there any way to detect this automatically (and reupload full debuginfo)?

from parca.