You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is problematic for consumers of libfdb_c.so, because there's no way to symbolicate a stack trace, and the FDB project cannot offer a .debug file with symbols (like how is done for all the server components), because no such file exists.
The text was updated successfully, but these errors were encountered:
As a side note, historically the debug file for libfdb_c.so had been named libfdb_c.so-debug, and I believe it was just an unstripped version of libfdb_c.so. This is different than what we do for the executables, where the .debug file contains just the symbols.
Currently, it appears that libfdb_c.so is stripped, and that this stripping does not generate a .debug file with symbols, unlike what is done for executables.
This is problematic for consumers of libfdb_c.so, because there's no way to symbolicate a stack trace, and the FDB project cannot offer a .debug file with symbols (like how is done for all the server components), because no such file exists.
The text was updated successfully, but these errors were encountered: