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
E.g. centos-atomic-host/7/x86_64/devel/continuous-debug. This would include the debuginfo RPMs of the gitoverlayed pkgs. Bonus points would be if the packages were actually compiled with CFLAGS="-g -Og" and gdb were added to the manifest. Since the continuous stream is primarily meant for users and developers to test upcoming features, we're bound to require frequent debugging as we get bug reports and verify functionality.
One might say we could just layer the debuginfo pkgs from the atomic-centos-continuous repo, but those only contain the RPMs for the last build, which might not always be what you want if you explicitly want to work in a previous version (e.g. when debugging something like coreos/rpm-ostree#306).
I'm for this. Would require some rpmdistro-gitoverlay work (inject CFLAGS) and rpm-ostree work (automatically add debuginfo).
That said...the clear long term is to do what Microsoft has been doing for ages and have a debuginfo/symbol server. Then one could use gdb without installing debuginfo packages or worrying about them staying in sync.
E.g.
centos-atomic-host/7/x86_64/devel/continuous-debug
. This would include the debuginfo RPMs of the gitoverlayed pkgs. Bonus points would be if the packages were actually compiled withCFLAGS="-g -Og"
andgdb
were added to the manifest. Since the continuous stream is primarily meant for users and developers to test upcoming features, we're bound to require frequent debugging as we get bug reports and verify functionality.One might say we could just layer the debuginfo pkgs from the
atomic-centos-continuous
repo, but those only contain the RPMs for the last build, which might not always be what you want if you explicitly want to work in a previous version (e.g. when debugging something like coreos/rpm-ostree#306)./cc @cgwalters
The text was updated successfully, but these errors were encountered: