Description of problem: When I start gdb on a process or attach it to an existing process, it scans for dependencies, and says where it cannot find the debugging symbols but doesn't say which debug packages should be installed as it used to say. Please make it say that, again. How reproducible: Always Steps to Reproduce: 1. gdb /bin/ls 2. r -lR / 3. Ctrl+C 4. bt.
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC.
CC: (none) => arnaud.patard, dmorganec, mageia, misc
Please give your output.
CC: (none) => krytarowski
(In reply to comment #2) > Please give your output. shlomif@telaviv1:~$ gdb /bin/ls GNU gdb (GDB) 7.3.50.20110722-2.mga2 (Mageia release 2) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /bin/ls...(no debugging symbols found)...done. (gdb)
^C Program received signal SIGINT, Interrupt. 0x00007ffff74f6a75 in __getdents64 () from /lib64/libc.so.6 (gdb) bt #0 0x00007ffff74f6a75 in __getdents64 () from /lib64/libc.so.6 #1 0x00007ffff74f6451 in readdir64 () from /lib64/libc.so.6 #2 0x000000000040793f in ?? () #3 0x0000000000408afd in ?? () #4 0x00007ffff7477c3d in __libc_start_main () from /lib64/libc.so.6 #5 0x00000000004026d9 in ?? () #6 0x00007fffffffdfa8 in ?? () #7 0x000000000000001c in ?? () #8 0x0000000000000003 in ?? () #9 0x00007fffffffe316 in ?? () #10 0x00007fffffffe31e in ?? () #11 0x00007fffffffe322 in ?? () #12 0x0000000000000000 in ?? () This is my result, is this right?
And this on the top: $ gdb /bin/ls GNU gdb (GDB) 7.1-6.mga1 (Mageia release 1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /bin/ls...(no debugging symbols found)...done. Missing debug package(s), you should install: coreutils-debug-8.8-2.mga1.x86_64 (gdb)
(In reply to comment #5) > And this on the top: > > $ gdb /bin/ls > GNU gdb (GDB) 7.1-6.mga1 (Mageia release 1) > Missing debug package(s), you should install: coreutils-debug-8.8-2.mga1.x86_64 > (gdb) But Shlomi speak about cauldron ;)
A yes... excuse me. I've reproduced this in the x86_64 Cauldron environment.
i will take a look to it
Assignee: bugsquad => dmorganec
Please test next gdb rpm.
(In reply to comment #9) > Please test next gdb rpm. With: gdb-7.3.50.20110722-3.mga2 I don't know if it's the ânextâ gdb rpm but it's the latest in the svn repository, I'm getting this: <QUOTE> shlomif@telaviv1:~$ gdb /bin/ls GNU gdb (GDB) 7.3.50.20110722-3.mga2 (Mageia release 2) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /bin/ls...(no debugging symbols found)...done. (gdb) </QUOTE> So it's still not good. Mageia Cauldron, x86-64. Regards, -- Shlomi Fish
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ D Morgan Please set status to ASSIGNED. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
Still valid.
please can we fix this bug before the release ? personnly I will never know wich package is necessary for debugging :(
Priority: Normal => High
Hi! I'd like to fix this bug. Can anyone give me some guidance on how to fix it? Does Mandriva or Fedora have a similar patch to gdb? Why did this functionality get broken in the first place? Regards, -- Shlomi Fish
(In reply to comment #14) > Hi! > > I'd like to fix this bug. Can anyone give me some guidance on how to fix it? Start with this patch: http://svnweb.mageia.org/packages/cauldron/gdb/current/SOURCES/gdb-7.1-buildid-locate-mageia.patch?revision=171528&view=markup&sortby=date > Does Mandriva or Fedora have a similar patch to gdb? Fedora is our upstream. > Why did this functionality > get broken in the first place? This is the question. > > Regards, > > -- Shlomi Fish
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Valid in Mageia 2.
Keywords: NEEDINFO => (none)Version: Cauldron => 2
Version: 2 => CauldronWhiteboard: (none) => MGA2TOO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
OK, here is some news. I discovered that the old gdb package tried to find librpm.so.2 instead of librpm.so.3 so I had to fix it, and it's available in the new package that I submitted just now: gdb-7.4.50.20120714-1.mga3 Furthermore, with the new package, I found a workaround to the bug. Just add this line: set build-id-verbose 2 to the file ~/.gdbinit and it will work again. It appears to be cancelled due to a conditional checking this variable by default, but I'm not sure why.
if it works fine on cauldron, any updates possible on mga2 ?
(In reply to comment #20) > if it works fine on cauldron, any updates possible on mga2 ? If Mga 2 is using librpm.so.2 then I believe no updates are needed in order to perform my workaround. If not, then we will need an update. Regards, -- Shlomi Fish
(In reply to comment #21) > (In reply to comment #20) > > if it works fine on cauldron, any updates possible on mga2 ? > > If Mga 2 is using librpm.so.2 then I believe no updates are needed in order to > perform my workaround. If not, then we will need an update. > Mga 2 is using librpm.so.2 (provided by lib64rpm2 or librpm2) Thx for the workaround, Shlomi, I added it in https://wiki.mageia.org/en/Debugging_software_crashes#gdb
(In reply to comment #22) > (In reply to comment #21) > > (In reply to comment #20) > > > if it works fine on cauldron, any updates possible on mga2 ? > > > > If Mga 2 is using librpm.so.2 then I believe no updates are needed in order to > > perform my workaround. If not, then we will need an update. > > > > Mga 2 is using librpm.so.2 (provided by lib64rpm2 or librpm2) > > Thx for the workaround, Shlomi, I added it in > https://wiki.mageia.org/en/Debugging_software_crashes#gdb You're welcome. Are we still seeking a more permanent fix? Regards, -- Shlomi Fish
(In reply to comment #23) > > Thx for the workaround, Shlomi, I added it in > > https://wiki.mageia.org/en/Debugging_software_crashes#gdb > > You're welcome. Are we still seeking a more permanent fix? > Yes, we are :) gdb is not only used by packagers/developers, but also by bug reporters who have never heard of gdb before, but are asked to use gdb to get a backtrace of their crash. A permanent fix will make getting that backtrace a bit less hard for them
Version: Cauldron => 2Whiteboard: MGA2TOO => (none)
Assignee: dmorganec => bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result and as this bug is fixed in mga3 we are closing it. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD