On Fri, 04 Jan 2008 17:53:09 +0100, Andrew Haley wrote: > Jan Kratochvil writes: ... > > OK, you are right Fedora GDB could; the build-id support messages should be > > cross-OS ones, this loading feature is still not imported into upstream GDB and > > it is heading there. > > Sure, but we could have a simple local message like > > Try "yum install /usr/lib/debug/.build-id/72/67a2ecd318b0f87a0747a6986d0d6dc01c6d8d.debug" > > I learnt only today that would work... Such as this one - just for the first such message printed? I guess changing the `Missing ...' message itself would be already too OS-specific. Starting program: /usr/bin/python Try: yum install /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug warning: Missing the separate debug info file: /usr/lib/debug/.build-id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug warning: Missing the separate debug info file: /usr/lib/debug/.build-id/e8/abaa654dc4b17b75c06c866898a17ea06f2bcf.debug [Thread debugging using libthread_db enabled] [New process 16964] warning: Missing the separate debug info file: /usr/lib/debug/.build-id/96/c005fcc474ab8b0d1aa41267111de2f0b647b0.debug warning: Missing the separate debug info file: /usr/lib/debug/.build-id/cd/19bdc5e57f1a00b2c7b4d6c6d1e3882d199ef9.debug warning: Missing the separate debug info file: /usr/lib/debug/.build-id/72/0ad477c75be7d7cbc97c0a6f443746dda98341.debug warning: Missing the separate debug info file: /usr/lib/debug/.build-id/ea/5b2fb654311e2dc8beacf2f19c1c6d172ba93d.debug ... Also removing the empty line (despite it may occasionally start in half of the screen) may help, I guess. Any other messaging feedback is welcome before it goes upstream. Thanks, Jan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
