Can't make GDB debug

MageSlayer · Joined: 29 Sep 2007 Posts: 5

Hi.

I'm trying to make gdb stop on breakpoints, but no luck. It just tells something like:

L · Joined: 01 Sep 2007 Posts: 21 Location: Germany

Hi,

I've also got problems with the debugger. Does yours ever hit any breakpoint? Have you compiled your program with the -g switch?

I've also got the problem, that gdb did not want to find the source file, but I can't remember, what I've done, so that it finally worked. I guess, it was the descent update.

[url] http://www.dsource.org/forums/viewtopic.php?t=2900 [/url]

I'm using descent v0.4.3.20070907 from svn and it still does not work as expected. The debugger hits the breakpoints and pauses the program, but descent doesn't switch to the debug view and I've got to use it manually, e.g. typing continue and so on...

MageSlayer · Joined: 29 Sep 2007 Posts: 5

asterite · Posted: Mon Oct 01, 2007 8:57 am Post subject:

Sorry for the delay, I wanted to see what others commented about this issue. If I test gdb in my virtual machine, it works. If you can send me a directory tree of the files you use for debugging, and also the functions, so that I can reproduce the problem, it would be great. You can generate di interface files for that.

Or maybe a description on what steps you use to compile and start debugging, where is the executable in relation to the project's path, etc. Another thing: I downloaded gdb and started using it: I applied no patch. (I'll tell you which version I'm using when I get home).

MageSlayer · Joined: 29 Sep 2007 Posts: 5

asterite · Posted: Mon Oct 01, 2007 9:14 am Post subject:

Cool, I'll test it at home this night and report back.

asterite · Posted: Tue Oct 02, 2007 9:36 pm Post subject:

Well, I tested your code. Compiling with gdc it works. I didn't test it with rebuild, but it should be the same. Can you try compiling it with gdb?

I'm using gdb 6.6-debian (I think it came installed in the Ubuntu I downloaded).

Also, if gdb doesn't find the source files, you can try sending it the following command:
directory <source_path>

After that, check if Descent finds a subsequent breakpoint. If it does, tell me so because that's the problem...

MageSlayer · Joined: 29 Sep 2007 Posts: 5

asterite · Posted: Wed Oct 03, 2007 7:37 am Post subject:

Sorry, I meant compiling with gdc.

I'll see what I can do with the other problem (the problem is, I can't reproduce it).

MageSlayer · Joined: 29 Sep 2007 Posts: 5

L · Joined: 01 Sep 2007 Posts: 21 Location: Germany

I've still got that problem with debugging D-programs

Symptoms: Everything works, except the automatic switch to the debug-view and debug-features.
I can run a small test application in debug mode. The debugger starts, but descent seems to behave as if a normal program has been run. I get the following output:

I installed the same deb-packages for rebuild/dsss, tango and tangobos from
http://download.palos.ro/Debian%20D%20Packages/binary/i386/
on a debian (etch?) system and the debug-view worked there.

asterite · Posted: Fri Jun 20, 2008 7:06 pm Post subject:

Ok... Now that I've switched to Ubuntu 8.04 (I used Windows before) I was able to test it... Indeed, the gdb version I used printed a breakpoint as

#n location at file:lineNumber address

but in the current gdb it's

#n location
at file:lineNumber address

I've fixed this in trunk. Since it'll be some time until the next release, the best you can do is use a trunk copy...

3-S-E · Joined: 16 Jun 2008 Posts: 54

But how to use a trunk copy? All I see are java-source-files there!
Is there an wiki / tutorial for this?

Why not releasing nightly builds of descent beside the stable-releases over svn. This would help us a lot and would give you better feedback!

EDIT: Okay, I've figured it out by myself and gdb works fine. There is only no console-output of your application because gdb uses console to tell you what it is doing...

For all who don't know how to update from trunk, here is my solution:

First you have to go here: http://www.dsource.org/projects/descent/browser/trunk

At the bottom of this page you will find a link with the headline "Download in other formats:".
Click on "Zip Archive" and a while later a download will start.

After download unpack the archive.
Open Eclipse with a new Workspace like "decent_trunk" in a directory of your choice
Click on "File" -> "Import"
Then "General" -> "Existing Projects into Workspace"
At "Select root directory" click an "Browse" and select the directory where you unpack the trunk-zip-file. This directory has to contain a lot of subdirectories like "decent.debug.core"

If you choose the proper directory a lot of projects will appear in the "Import Projects"-form.
Select "Copy projects into workspace" (if your trunk-folder isn't already in the workspace-folder). I didn't select this checkbox because I've already copied the trunk folder properly into workspace before import. Try it out by yourself.

Click "Finish"!

Okay, now a bunch of projects should appear at the "Project Explorer"
Eclipse should now do a full rebuild on this workspace... if it doesn't, click on "Project" at the upper menu and "Build all", or try "F5" for an refresh...
After a while of rebuilding there should be at least no errors (red crosses beside the icons at Project-Explorer) at the descent.debug.core project.

And now how I managed to update the plug-in (I did it with Windows and 7Zip):

(Make sure eclipse is closed!)

I've opened the directory containing the newly build class-files at my workspace-directory -> "descent.debug.core/bin/descent/internal/debug/core/model/gdb"
Then I've opened the jar-archive at the eclipse installation directory (linux: "/home/USERNAME/.eclipse/org.eclipse.sdk.ide/updates/eclipse/plugins" - file: "descent.debug.core_0.5.2.20080501.jar") with 7zip and replaced
the "Running.class"-File with the newly build one (at ubuntu 8.04 you have the "archive-manager" for this).

Okay... that's it!

Run Eclipse, open a Workspace / D-Project and do your gdb-debugging.

Hope that will help some of you.

asterite · Posted: Sat Jun 21, 2008 12:56 pm Post subject:

Wow, S-3-E, that's very useful, thank you! I don't know if I have to give permissions to allow anyone to write in the wiki. If you could do a wiki page in Descent for it, that would be great.

Instead of replacing the class files in the plugins, you can create them from the project itself. Just open the file site.xml in the descent.update-site project and click "Build All". After the build is finished, you should have the new plugins in the plugins directory.

I would like to have nightly builds, but I'm not familiar with how to do that, nor I have the time for it. Also, there are times where the code is kind of unstable, mostly because the project is just beginning... If anyone wants to care about nightly builds (I guess it's just about updating to the latest trunk and building all... maybe an ant.xml for that), he's welcome to join the project. Smile

I'm glad the debugger is finally working for you. Very Happy

3-S-E · Joined: 16 Jun 2008 Posts: 54

No problem! I like D and I think Descent is one of the most promising plug-ins for the brilliant Eclipse-IDE.

I would love to have access privilege to the wiki, though my english is not that good... Embarassed

Nontheless it would be a pleasure for me to help, maybe I can do some translation of the ui into german language?!

Back to topic: The debugging works fine now under Ubuntu, but the gdc support lacks further on. Atm I switched back to windows to work on my project (with dmd). Tomorrow, if I have some time left over, I'll try to figure out, what's wrong with my config!