|
From: Dennis L. <pla...@in...> - 2006-02-09 22:01:50
|
Hello, I have recently discovered on the SuSE 10.0 Linux Distribution that there are "debuginfo" packages for lots of installed packages. After installing it for one of the apps I have installed, the ?? in the stacktrace of gdb disappeared and I actually got usefuly output. I have looke a bit further in it, and it installed the sources and some special looking files. Now the question is, if its possible to get those external infos somehow into valgrind too? Sorry to give so few information about how its working, I couldnt really figure out. greets Dennis |
|
From: Julian S. <js...@ac...> - 2006-02-09 22:21:28
|
So I thought we have had the ability to read debuginfo packages for ages (Tom H will know for sure). Maybe it got broken by recent hacking. (if so, we should regression-test it somehow). What V version are you using? J On Thursday 09 February 2006 22:01, Dennis Lubert wrote: > Hello, > > I have recently discovered on the SuSE 10.0 Linux Distribution that > there are "debuginfo" packages for lots of installed packages. After > installing it for one of the apps I have installed, the ?? in the > stacktrace of gdb disappeared and I actually got usefuly output. I have > looke a bit further in it, and it installed the sources and some special > looking files. Now the question is, if its possible to get those > external infos somehow into valgrind too? Sorry to give so few > information about how its working, I couldnt really figure out. > > greets > > Dennis > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Dennis L. <pla...@in...> - 2006-02-09 22:25:14
|
Am Donnerstag, den 09.02.2006, 22:21 +0000 schrieb Julian Seward: > So I thought we have had the ability to read debuginfo packages for > ages (Tom H will know for sure). Maybe it got broken by recent hacking. > (if so, we should regression-test it somehow). What V version are > you using? SVN |
|
From: Nicholas N. <nj...@cs...> - 2006-02-09 23:07:56
|
On Thu, 9 Feb 2006, Julian Seward wrote: >> I have recently discovered on the SuSE 10.0 Linux Distribution that >> there are "debuginfo" packages for lots of installed packages. After >> installing it for one of the apps I have installed, the ?? in the >> stacktrace of gdb disappeared and I actually got usefuly output. I have >> looke a bit further in it, and it installed the sources and some special >> looking files. Now the question is, if its possible to get those >> external infos somehow into valgrind too? Sorry to give so few >> information about how its working, I couldnt really figure out. > > So I thought we have had the ability to read debuginfo packages for > ages (Tom H will know for sure). Maybe it got broken by recent hacking. > (if so, we should regression-test it somehow). What V version are > you using? If the debuginfo packages are not installed for the app then Valgrind can't take advantage of them... this seems like an issue with the app and its installation rather than Valgrind. Nick |
|
From: Tom H. <to...@co...> - 2006-02-09 23:04:18
|
In message <1139522500.27095.6.camel@speedy>
Dennis Lubert <pla...@in...> wrote:
> I have recently discovered on the SuSE 10.0 Linux Distribution that
> there are "debuginfo" packages for lots of installed packages. After
> installing it for one of the apps I have installed, the ?? in the
> stacktrace of gdb disappeared and I actually got usefuly output. I have
> looke a bit further in it, and it installed the sources and some special
> looking files. Now the question is, if its possible to get those
> external infos somehow into valgrind too? Sorry to give so few
> information about how its working, I couldnt really figure out.
These should already be found and used by valgrind automatically. I've
never tried it with SuSE but it certainly works with Fedora. If you run
with -v then you should see something like this:
--20714-- Reading syms from /lib/libc-2.3.5.so (0x2B6000)
--20714-- Reading debug info from /usr/lib/debug/lib/libc-2.3.5.so.debug...
Showing that it has read debug information from the debug files installed
from the debuginfo package.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Dennis L. <pla...@in...> - 2006-02-09 23:33:40
|
Am Donnerstag, den 09.02.2006, 23:04 +0000 schrieb Tom Hughes: > These should already be found and used by valgrind automatically. I've > never tried it with SuSE but it certainly works with Fedora. If you run > with -v then you should see something like this: > > --20714-- Reading syms from /lib/libc-2.3.5.so (0x2B6000) > --20714-- Reading debug info from /usr/lib/debug/lib/libc-2.3.5.so.debug... > > Showing that it has read debug information from the debug files installed > from the debuginfo package. Wow, I didnt even thought about that valgrind could already support it :) From failing to use them I errenously inferred that it doesnt. So now that I know it does, I will further look what went wrong, and if its Vs fault will come back :) greets Dennis |