Re: [Bug 395077] Detect that there's no debugging info

[Seemanta Dutta <seemanta gmail com>]

Hi Dodji/Jonner,
My idea was that we can implement very basic checking for debugging info first, and then on top of it implement a PackageKit based solution later on. If I am right, a PackageKit based solution will work only for standard programs, right? For user created programs, the user has no option but to generate the elf with debugging information. Am I right?

So I propose to:

1. Implement a very basic detection system for lack of debugging info.
2. Later on integrate PackageKit to detect lack of debugging info *and* also propose downloading the debugging info, if the user wishes so.

I am planning to work on 1. first and then later on 2., i.e. develop PackageKit based solution. Does this approach sound good?

Coming to 1., well I actually did some bit of research on how to detect debugging info. When I run gdb on a program without debugging info, I get this message: 
"Reading symbols from /home/seemanta/Development/bin/nemiver/bin/hello...(no debugging symbols found)...done."

Here, I wrote a 'hello world' program, which did not have any debugging information. My first thought is to intercept the place in nemiver where this message is received. I would really appreciate it if you pointed me to that place in the Nemiver source tree.
That would be a good point to detect lack of debugging symbols, am I right? The solution to 1. should work its way up from there. Awaiting your comments before proceeding forward and thanks as usual for helping me out :)

regards,
Seemanta

On Thu, May 27, 2010 at 6:14 PM, nemiver <bugzilla gnome org> wrote:

https://bugzilla.gnome.org/show_bug.cgi?id=395077
 nemiver | general | trunk

--- Comment #5 from dodji seketeli <dodji seketeli org> 2010-05-27 12:44:24 UTC ---
Btw, Seemanta, I have assigned you the bug as you asked :-)

--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.