RE: [Anjuta-list] Hello...

["Yitzhak Sapir" <yitzhaks actimize com>]

Thanks for the quick reply.  

> -----Original Message-----
> From: Naba Kumar [mailto:kh_naba gmx net]
> Sent: Sunday, November 24, 2002 7:43 PM
> To: Yitzhak Sapir
> Cc: Anjuta List
> Subject: Re: [Anjuta-list] Hello...
> 
> 
> On Sun, 2002-11-24 at 19:23, Yitzhak Sapir wrote:
> > 
> > When I start up anjuta, gnome-terminal complains:
> > "Error on option --diable-factory: unknown option."
> >
> That option is only valid for gnome2 version of gnome-terminal, which
> apparently is not installed in your system. Anjuta is *suppose* to
> verify this at startup and decide if it should use the 
> --disable-factory
> option for gnome-terminal or not, but apparently it isn't working in
> your case.

I think it is working but not perfectly user-friendly (IMO).  In my opinion a user-friendly interface won't send output of verification procedures to the console.  Just serious errors.

> Please send the debug output from anjuta so that we could 
> study it. You
> will have to pass the --with-debug option during anjuta configuration
> and build it to get the debug outputs.

Is it possible to keep two executables: anjuta-debug and anjuta?  If so, is there anything special I should do ahead of time.

> Also, if possible, please send the output of:
> gnome-terminal --version

I should point out that I self compiled a lot of libraries, and downloaded others as binaries when I could (and the binaries were valid -- some binaries like gnome-vfs assumed oaf was installed in a different directory than the make install put it in).  In any case, for my case, the Gnome Terminal output is:
Gnome Terminal 1.4.0.4

> 
> Mean time, you can avoid using gnome-terminal, by going to
> [Settings->Commands->Terminal command] (select xterm. It should work
> fine).

This output comes out only on startup and apparently it's the result of the check of whether --disable-factory is valid.  I do not indeed have gnome2, because I had trouble compiling it, and it seems Sun in its home page only has a beta gnome2 system released.  So I guess gnome2 is not that stable yet, as far as Sun sparc solaris is concerned.  The output of this --disable-factory check could have been passed to /dev/null or a pipe to eliminate it being shown on the command line from where I ran anjuta.  (For now, I run anjuta from the command line).  Also, it's spelled "diable-factory" in some places in the code (no s).  I assume that is a bug.

> > PR_SYSEXIT: Exit from a traced system call Exit from SYS_execve
> > PR_SYSEXIT: Exit from a traced system call Exit from SYS_execve
> > PR_FAULTED: Incurred a traced hardware fault FLTBT: Breakpoint trap
> > PR_FAULTED: Incurred a traced hardware fault FLTTRACE: Trace trap
> > PR_FAULTED: Incurred a traced hardware fault FLTBT: Breakpoint trap
> > Reading symbols... done
> > PR_FAULTED: Incurred a traced hardware fault FLTTRACE: Trace trap
> > PR_FAULTED: Incurred a traced hardware fault FLTBT: Breakpoint trap
> > main() at main.cc:9
> > 
> Looks like some gdb screw up. It will require someone with 
> sparc system
> to spend some time investigating it. May be we need to pass 
> some options
> to gdb initialization, but I am not sure.

Is there any simple way for me to verify it?  Any thing I can do to the source to see the full gdb input/output session, so I can reproduce it on gdb and try to figure out what's wrong?  Will this be in the debug output?

Also, I'm signed on the users-list.  If I go this way would it be more appropriate to go to the development list?

Thanks again for your help.