Re: [Anjuta-list] Basic problems with Anjuta

[Sébastien Granjoux <seb sfo free fr>]

Hi

Steve a écrit :
> I have seen debuggers that display assembly code when there is no source code
> or symbol information to display. Anjuta's behaviour is OK as long as 
we know
> what it is going to do and it always does the same thing.

Yes but I don't know if it's possible with gdb. You can still go into 
the function using the assembler view and stepping at assembler level.

> It would be OK if Anjuta just stepped over the gtk_init() to the next line
> just as it stepped over gtk_set_locale() but it didn't. It appears to 
have
> executed a Continue command and run the program to the end which in this
> case is an infinite loop.

Ok, I think I understand your case. There is an issue with step when a 
dynamic library is loaded.

In Anjuta, it is possible to put breakpoint in dynamic libraries. It 
means in piece code which are not loaded when the program starts. To do 
this, Anjuta gets a signal each time a new library is loaded and check 
if it can place additional breakpoints. The problem is that this signal 
interrupt the current gdb operation step, run or whatever and Anjuta 
doesn't know which one. So, in all case Anjuta restart gdb with 
continue. If you were doing a step operation, you have no luck and the 
program will not stop.

I have added a note in the documentation on Anjuta 2.24 about this 
(chapter 6.2.2), I hope it is clear enough.

Since that time, gdb has been improved and there is now a better way to 
do this but it is currently not used by Anjuta.

> Anjuta starts up with a list of files in the left hand pane and nothing
> in the right hand pane. Debug is available in the menu. Why is this?
> Since I used the -n flag I was expecting Anjuta to start as if it was
> being run for the first time.

I think the debugger plugin is in the list of default plugin, so you get 
it if you use -n option. It is probably not in the default list of new 
project, so you don't get it when you create a new project. I'm not 
completely sure though.

> From the File menu, select New and then Project. 
> The "Application Assistent" is started. (Note the typo - that should be Assistant)

This bug has been fixed in 2.24 I think.

> Select Forward. The Project Type window is displayed with the 'C' tab visible.
> Select GTK+ and click Forward. The Basic Information window is displayed.
>...

I have repeated the same things. You have hit several bugs:

1. The preferences are not saved correctly the first time.
http://bugzilla.gnome.org/show_bug.cgi?id=307886

2. There is problem to set the yellow arrow
http://bugzilla.gnome.org/show_bug.cgi?id=559867

3. The problem with dynamic libraries and step that I have explained above.

Regards,

Sébastien