"find-dbgsym-packages /usr/bin/gio" command outputs errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-goodies (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am not sure if this problem is caused by my not doing this right, a bug in gdb, a bug in gio, or a fault in the source libraries server. But after four days no one has an answer to this problem at my thread at: https:/
The goal is the ability to step through gio's source code to follow its execution to find out why it is not working for me in my main account (account ID 1000), but does work in other accounts created susequently for testing. To get symbols, and source code, I followed the directions at:
https:/
duginfod did not work on my Ubuntu 22.04 system. It was therefore necessary to do a manual download. I followed the directions under the heading "Getting -dbgsym.ddeb packages", and then "Automatic Resolution / Installation of necessary packages", on that page. All went well until the find-dbgsym-
stephen@stephen:~$ find-dbgsym-
dpkg-query: no path found matching pattern /lib/x86_
W: Cannot find debug package for /lib/x86_
dpkg-query: no path found matching pattern /lib/x86_
W: Cannot find debug package for /lib/x86_
dpkg-query: no path found matching pattern /lib/x86_
W: Cannot find debug package for /lib/x86_
dpkg-query: no path found matching pattern /lib/x86_
W: Cannot find debug package for /lib/x86_
dpkg-query: no path found matching pattern /lib/x86_
W: Cannot find debug package for /lib/x86_
libblkid1-dbgsym libffi8-dbgsym libglib2.
I interpret these errors to mean that the packages the find-dbgsym-
For the details regarding my need to step through code see this thread of mine:
https:/
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/2009526/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]