gubed-devel — Developer and user discussions

Re: [gbd-dev] regexptest.php not up to date?

[Brett S. <tec...@se...>]

Varies.   I do see php errors thru the webserver, but not all or always.
 Sometimes I just get a blank page and then if I run manually I get the
errors, other times I see the errors thru the webserver.  This behavior
seems to vary depending on which webserver I use on which platform. 
When I'm not sure, I run manually.

I've started playing with php5 and see that the cli and cgi binaries are
now separate.

Brett

On Thu, 7 Jul 2005 06:47:50 +0200, "Linus McCabe" <Li...@mc...>
said:
> 
> Hi
> 
> Do you mean that if you run through the webserver it does not show the
> error, 
> but it does if you run cli version?
> 
> Thats the behaviour i see when turning off display_errors anyway (it
> seems 
> that setting has no meaning for cli version of php?)
> 
> /Linus
> 
> On Thursday 07 July 2005 03.17, Brett Serkez wrote:
> > I run php from the command line against my php files to see errors,
> > either the DOS box on Windows or an xterm on Linux.  Php has an option
> > -f used to suppress the HTML headers in this case.
> >
> > Brett
> >
> > On Wed, 06 Jul 2005 20:30:18 -0400, "Iassen Hristov"
> >
> > <ihr...@da...> said:
> > > I guess my problem is that the version of PHP I have for some reason is
> > > not
> > > giving out any error information. It just quits with no error message
> > > whatsoever. This happened to me several times while debugging.
> > >
> > > It must be a problem with the compilation of PHP (I am using the
> > > apache2triad package which has it pre-compiled).
> > >
> > > This is why I don't see the errors as you see them.
> > >
> > > For example:
> > > > C:\apache2triad\htdocs\owl\phplib>php -l test_mssql.php
> > > > Errors parsing test_mssql.php
> > >
> > > Gives me only this "Errors parsing test_mssql.php". Nothing more.
> > >
> > > Executing the same thing on a Linux box (again PHP 5.0.4) returns a
> > > normal
> > > error as expected
> > >
> > > > Parse error: parse error, unexpected ';' in test_mssql.php on line 21
> > > > Errors parsing test_mssql.php
> > >
> > > --On Wednesday, July 06, 2005 22:11 +0200 Linus McCabe <Li...@mc...>
> > >
> > > wrote:
> > > > On Wednesday 06 July 2005 21.44, Iassen Hristov wrote:
> > > >> It looks like the content of Gubed/ServerScripts/develop/ is not up to
> > > >> date, because I do not get an explanation (and a link) on which line
> > > >> is the error.
> > > >
> > > > Well, regexptest only gives you a link if the original file is error
> > > > free (ie,  its made to find errors in Gubeds parser, not to find errors
> > > > in you php  files)
> > > >
> > > > However, you can still make it test the file by doing something like:
> > > > http://server/Gubed/ServerScripts/develop/diffdisplay.php?file=C:/apach
> > > >e2 triad/htdocs/owl/phplib/test_mssql.php
> > > >
> > > > it will then show the original and parsed file as usual, but also the
> > > > original  file will have an error. In you specific case, its the
> > > > missing parenthesis at  the bottom (if you didnt already know).
> > > > Once thats taken care of, it parses fine both before and after gubed's
> > > > alternations.
> > > >
> > > > /linus
> > >
> > > -------------------------------------------------------
> > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > informative Webcasts and more! Get everything you need to get up to
> > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > _______________________________________________
> > > Gubed-devel mailing list
> > > Gub...@li...
> > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> >
> > -------------------------------------
> > Brett C. Serkez, Technical Trainer
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Gubed-devel mailing list
> > Gub...@li...
> > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] regexptest.php not up to date?

[Linus M. <Li...@mc...>]

Hi

Do you mean that if you run through the webserver it does not show the error, 
but it does if you run cli version?

Thats the behaviour i see when turning off display_errors anyway (it seems 
that setting has no meaning for cli version of php?)

/Linus

On Thursday 07 July 2005 03.17, Brett Serkez wrote:
> I run php from the command line against my php files to see errors,
> either the DOS box on Windows or an xterm on Linux.  Php has an option
> -f used to suppress the HTML headers in this case.
>
> Brett
>
> On Wed, 06 Jul 2005 20:30:18 -0400, "Iassen Hristov"
>
> <ihr...@da...> said:
> > I guess my problem is that the version of PHP I have for some reason is
> > not
> > giving out any error information. It just quits with no error message
> > whatsoever. This happened to me several times while debugging.
> >
> > It must be a problem with the compilation of PHP (I am using the
> > apache2triad package which has it pre-compiled).
> >
> > This is why I don't see the errors as you see them.
> >
> > For example:
> > > C:\apache2triad\htdocs\owl\phplib>php -l test_mssql.php
> > > Errors parsing test_mssql.php
> >
> > Gives me only this "Errors parsing test_mssql.php". Nothing more.
> >
> > Executing the same thing on a Linux box (again PHP 5.0.4) returns a
> > normal
> > error as expected
> >
> > > Parse error: parse error, unexpected ';' in test_mssql.php on line 21
> > > Errors parsing test_mssql.php
> >
> > --On Wednesday, July 06, 2005 22:11 +0200 Linus McCabe <Li...@mc...>
> >
> > wrote:
> > > On Wednesday 06 July 2005 21.44, Iassen Hristov wrote:
> > >> It looks like the content of Gubed/ServerScripts/develop/ is not up to
> > >> date, because I do not get an explanation (and a link) on which line
> > >> is the error.
> > >
> > > Well, regexptest only gives you a link if the original file is error
> > > free (ie,  its made to find errors in Gubeds parser, not to find errors
> > > in you php  files)
> > >
> > > However, you can still make it test the file by doing something like:
> > > http://server/Gubed/ServerScripts/develop/diffdisplay.php?file=C:/apach
> > >e2 triad/htdocs/owl/phplib/test_mssql.php
> > >
> > > it will then show the original and parsed file as usual, but also the
> > > original  file will have an error. In you specific case, its the
> > > missing parenthesis at  the bottom (if you didnt already know).
> > > Once thats taken care of, it parses fine both before and after gubed's
> > > alternations.
> > >
> > > /linus
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Gubed-devel mailing list
> > Gub...@li...
> > https://lists.sourceforge.net/lists/listinfo/gubed-devel
>
> -------------------------------------
> Brett C. Serkez, Technical Trainer
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

Re: [gbd-dev] regexptest.php not up to date?

[Linus M. <Li...@mc...>]

On Thursday 07 July 2005 02.30, Iassen Hristov wrote:
> I guess my problem is that the version of PHP I have for some reason is not
> giving out any error information. It just quits with no error message
> whatsoever. This happened to me several times while debugging.

Check your php.ini for the display_errors setting, is it on?

/linus

Re: [gbd-dev] regexptest.php not up to date?

[Brett S. <tec...@se...>]

I run php from the command line against my php files to see errors,
either the DOS box on Windows or an xterm on Linux.  Php has an option
-f used to suppress the HTML headers in this case.

Brett

On Wed, 06 Jul 2005 20:30:18 -0400, "Iassen Hristov"
<ihr...@da...> said:
> I guess my problem is that the version of PHP I have for some reason is
> not
> giving out any error information. It just quits with no error message
> whatsoever. This happened to me several times while debugging.
> 
> It must be a problem with the compilation of PHP (I am using the
> apache2triad package which has it pre-compiled).
> 
> This is why I don't see the errors as you see them.
> For example:
> 
> > C:\apache2triad\htdocs\owl\phplib>php -l test_mssql.php
> > Errors parsing test_mssql.php
> 
> Gives me only this "Errors parsing test_mssql.php". Nothing more.
> 
> Executing the same thing on a Linux box (again PHP 5.0.4) returns a
> normal
> error as expected
> 
> > Parse error: parse error, unexpected ';' in test_mssql.php on line 21
> > Errors parsing test_mssql.php
> 
> 
> --On Wednesday, July 06, 2005 22:11 +0200 Linus McCabe <Li...@mc...>
> wrote:
> 
> > On Wednesday 06 July 2005 21.44, Iassen Hristov wrote:
> >> It looks like the content of Gubed/ServerScripts/develop/ is not up to
> >> date, because I do not get an explanation (and a link) on which line is
> >> the error.
> > 
> > Well, regexptest only gives you a link if the original file is error free
> > (ie,  its made to find errors in Gubeds parser, not to find errors in you
> > php  files)
> > 
> > However, you can still make it test the file by doing something like:
> > http://server/Gubed/ServerScripts/develop/diffdisplay.php?file=C:/apache2
> > triad/htdocs/owl/phplib/test_mssql.php
> > 
> > it will then show the original and parsed file as usual, but also the
> > original  file will have an error. In you specific case, its the missing
> > parenthesis at  the bottom (if you didnt already know).
> > Once thats taken care of, it parses fine both before and after gubed's 
> > alternations.
> > 
> > /linus
> > 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] regexptest.php not up to date?

[Iassen H. <ihr...@da...>]

I guess my problem is that the version of PHP I have for some reason is not
giving out any error information. It just quits with no error message
whatsoever. This happened to me several times while debugging.

It must be a problem with the compilation of PHP (I am using the
apache2triad package which has it pre-compiled).

This is why I don't see the errors as you see them.
For example:

> C:\apache2triad\htdocs\owl\phplib>php -l test_mssql.php
> Errors parsing test_mssql.php

Gives me only this "Errors parsing test_mssql.php". Nothing more.

Executing the same thing on a Linux box (again PHP 5.0.4) returns a normal
error as expected

> Parse error: parse error, unexpected ';' in test_mssql.php on line 21
> Errors parsing test_mssql.php


--On Wednesday, July 06, 2005 22:11 +0200 Linus McCabe <Li...@mc...>
wrote:

> On Wednesday 06 July 2005 21.44, Iassen Hristov wrote:
>> It looks like the content of Gubed/ServerScripts/develop/ is not up to
>> date, because I do not get an explanation (and a link) on which line is
>> the error.
> 
> Well, regexptest only gives you a link if the original file is error free
> (ie,  its made to find errors in Gubeds parser, not to find errors in you
> php  files)
> 
> However, you can still make it test the file by doing something like:
> http://server/Gubed/ServerScripts/develop/diffdisplay.php?file=C:/apache2
> triad/htdocs/owl/phplib/test_mssql.php
> 
> it will then show the original and parsed file as usual, but also the
> original  file will have an error. In you specific case, its the missing
> parenthesis at  the bottom (if you didnt already know).
> Once thats taken care of, it parses fine both before and after gubed's 
> alternations.
> 
> /linus
> 

Re: [gbd-dev] Parsing error

[Iassen H. <ih...@da...>]

> If you dont mind, Ill mind the previous post ;)
> 
> It should work just as well with POST as GET. If I modify the testbench
> sample  of a html form to use post, it works as well.

You are correct, it works with POST as well.

> 
> Anyway, about your mssql problem, is that problem there wether you use
> gubed  or not?

Yes. The problem is still there with or without gubed. Everything is as
expected.

BTW: I fixed it (to the extend it is possible) for MSSQL. I will post the
modifications to the OWL project.

If you would allow me a comment:

Gubed is an excellent application. The only thing I had real trouble with,
is when it does not like much the file it tries to debug. For example the 
owl.lib.php file gave me these warnings, which are non-fatal.

12:54:16: Warning: C:\apache2triad\htdocs\owl\lib\owl.lib.php, line 34,
error 8: import_request_variables(): No prefix specified - possible
security hazard
12:54:16: Warning: C:\apache2triad\htdocs\owl\lib\owl.lib.php, line 64,
error 8: Use of undefined constant currentdb - assumed 'currentdb'
12:54:16: Warning: C:\apache2triad\htdocs\owl\lib\owl.lib.php, line 70,
error 8: Use of undefined constant currentdb - assumed 'currentdb'

When it does this you can step trough it, but you don't see the context and
when the problem is in this file you are required to fix the warnings, even
though it passes the parsing test.

Thanks much for the help.

---
Iassen Hristov

Re: [gbd-dev] regexptest.php not up to date?

[Linus M. <Li...@mc...>]

On Wednesday 06 July 2005 21.44, Iassen Hristov wrote:
> It looks like the content of Gubed/ServerScripts/develop/ is not up to
> date, because I do not get an explanation (and a link) on which line is the
> error.

Well, regexptest only gives you a link if the original file is error free (ie, 
its made to find errors in Gubeds parser, not to find errors in you php 
files)

However, you can still make it test the file by doing something like:
http://server/Gubed/ServerScripts/develop/diffdisplay.php?file=C:/apache2triad/htdocs/owl/phplib/test_mssql.php

it will then show the original and parsed file as usual, but also the original 
file will have an error. In you specific case, its the missing parenthesis at 
the bottom (if you didnt already know).
Once thats taken care of, it parses fine both before and after gubed's 
alternations.

/linus

> All I get is:
>
> C:/apache2triad/htdocs/owl/phplib/test_mssql.php 55 lines Original file did
> not parse
>
> I am attaching the source of the full output HTML and the test_mssql.php
> file that has the problem. I am sure it does have some syntax error in it,
> so I am sure it is not an issue of parsing, but simply it does not display
> what the error is.
>
> I guess one peculiar thing is, I am running under MS Windows. PHP is 5.0.4,
> not that it should matter.
>
> --On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
>
> wrote:
> > Hi!
> >
> > It was a while ago since a parsing error was reported...
> > Replace your GubedParserTokenizer.php file with the attached one and it
> > should  work better.
> >
> > About regexptest:
> > I took the file you sent me and put it on my computer, in the dir
> > "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
> >
> > Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
> > where  i put the file)
> >
> > Then when i click "search" i get:
> >
> > ...
> > 1: ./testcode.php 3837 lines T_ARRAY: 'array'
> >    ***   Did not parse ok!   ***
> > 2: ./regexptestcode.php 375 lines Parsed ok!
> > 3: ./diffdisplay.php 123 lines Parsed ok!
> > 4: ./index.php 26 lines Parsed ok!
> > 5: ./postprocessdiff.php 68 lines Parsed ok!
> > 6: ./regexptest.php 239 lines Parsed ok!
> > 7: ./postprocess.php 21 lines Parsed ok!
> > 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
> > ...
> >
> > Ie, it tells me it could parse all files except the one you gave me
> > (which i  saved as testcode.php when i saved it from the browser)
> >
> > I can then click on 'Did not parse ok' which is a link.
> >
> > Gubed will now show the code in modified (parsed) and unmodified versions
> > side  by side as well as tell you what line it fails on. Sometimes the
> > line is not  exact, since a parse error from gubed can result in a syntax
> > error further  down (just like php give you the wrong line number
> > sometimes).
> >
> > I find the line it tells me and compare the parsed code to the original
> > and  figure out what went wrong, this time it was very easy...
> >
> > Anyway, you can always send unparsable files if you dont want to do this
> > work  yourself.
> > You're also encouraged to do the "Start scanning entire system
> > (*nix/Linux  only)" on regexptest.php if you can and see if you have
> > other unparsable  files...
> >
> > Thanks for reporting the bug and let me know if it works better now!
> >
> > cheers
> > /Linus

[gbd-dev] regexptest.php not up to date?

[Iassen H. <ih...@da...>]

It looks like the content of Gubed/ServerScripts/develop/ is not up to
date, because I do not get an explanation (and a link) on which line is the
error.

All I get is:

C:/apache2triad/htdocs/owl/phplib/test_mssql.php 55 lines Original file did
not parse

I am attaching the source of the full output HTML and the test_mssql.php
file that has the problem. I am sure it does have some syntax error in it,
so I am sure it is not an issue of parsing, but simply it does not display
what the error is.

I guess one peculiar thing is, I am running under MS Windows. PHP is 5.0.4,
not that it should matter.

--On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
wrote:

> 
> Hi!
> 
> It was a while ago since a parsing error was reported... 
> Replace your GubedParserTokenizer.php file with the attached one and it
> should  work better.
> 
> About regexptest:
> I took the file you sent me and put it on my computer, in the dir 
> "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
> 
> Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
> where  i put the file)
> 
> Then when i click "search" i get:
> 
> ...
> 1: ./testcode.php 3837 lines T_ARRAY: 'array' 
>    ***   Did not parse ok!   ***
> 2: ./regexptestcode.php 375 lines Parsed ok!
> 3: ./diffdisplay.php 123 lines Parsed ok!
> 4: ./index.php 26 lines Parsed ok!
> 5: ./postprocessdiff.php 68 lines Parsed ok!
> 6: ./regexptest.php 239 lines Parsed ok!
> 7: ./postprocess.php 21 lines Parsed ok!
> 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
> ...
> 
> Ie, it tells me it could parse all files except the one you gave me
> (which i  saved as testcode.php when i saved it from the browser)
> 
> I can then click on 'Did not parse ok' which is a link.
> 
> Gubed will now show the code in modified (parsed) and unmodified versions
> side  by side as well as tell you what line it fails on. Sometimes the
> line is not  exact, since a parse error from gubed can result in a syntax
> error further  down (just like php give you the wrong line number
> sometimes).
> 
> I find the line it tells me and compare the parsed code to the original
> and  figure out what went wrong, this time it was very easy...
> 
> Anyway, you can always send unparsable files if you dont want to do this
> work  yourself.
> You're also encouraged to do the "Start scanning entire system
> (*nix/Linux  only)" on regexptest.php if you can and see if you have
> other unparsable  files...
> 
> Thanks for reporting the bug and let me know if it works better now!
> 
> cheers
> /Linus

Re: [gbd-dev] Parsing error

[Linus M. <Li...@mc...>]

Hello!

If you dont mind, Ill mind the previous post ;)

It should work just as well with POST as GET. If I modify the testbench sample 
of a html form to use post, it works as well.

Anyway, about your mssql problem, is that problem there wether you use gubed 
or not?

/Linus

On Wednesday 06 July 2005 19.19, Iassen Hristov wrote:
> Never mind the previous post.
> I had a mistake in the modification for the GET I did.
> It works now.
> Thanks a million.
>
> For the record the problem seems to be on the line
> $dNow = $sql->now();
>
> Apparently PHP blows up on this when used with MSSql. Now need to figure
> out why and fix it.
>
> Thanks again for your help.
>
> --On Wednesday, July 06, 2005 12:46 -0400 Iassen Hristov
>
> <ih...@da...> wrote:
> > Thank you.
> > Now I can debug. However I need one clarification:
> >
> > How do I debug a page that expects POST data as input?
> > I could not find an example of how to do this.
> > Or am I way off target here and I am supposed to be debugging in some
> > completely different way?
> >
> > Right now I can debug trough the index.php, but at the end it sends me to
> > the same page (in the browser), because I need to input user name and
> > password. I tried modifying the page to use GET (instead of POST) and
> > provide the user name and password in the params, but it does not seem to
> > be passing them.
> >
> > In other words I provide
> > /index.php?login=1&loginname=admin&password=admin
> >
> > As the input in the StartSession page.
> > <http://localhost/gubed/StartSession.php>
> >
> > BTW: The problem I am trying to debug is this:
> > I installed OWL on a Windows computer. It works fine when hitting a
> > PostgreSQL database. However when I change it to use MSSql instead of
> > Postgre I can't login. I traced the SQL statements it sends to the server
> > and it seems fine up to a certain point. There are no errors whatsoever,
> > but then it just finishes and sends me again to the login page. I suspect
> > there is some kind of subtle error in the invoking code that somehow
> > manifests itself only in the mssql library (or the returned result is
> > somehow different and that messes it up).
> >
> >
> > --On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
> >
> > wrote:
> >> Hi!
> >>
> >> It was a while ago since a parsing error was reported...
> >> Replace your GubedParserTokenizer.php file with the attached one and it
> >> should  work better.
> >>
> >> About regexptest:
> >> I took the file you sent me and put it on my computer, in the dir
> >> "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
> >>
> >> Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
> >> where  i put the file)
> >>
> >> Then when i click "search" i get:
> >>
> >> ...
> >> 1: ./testcode.php 3837 lines T_ARRAY: 'array'
> >>    ***   Did not parse ok!   ***
> >> 2: ./regexptestcode.php 375 lines Parsed ok!
> >> 3: ./diffdisplay.php 123 lines Parsed ok!
> >> 4: ./index.php 26 lines Parsed ok!
> >> 5: ./postprocessdiff.php 68 lines Parsed ok!
> >> 6: ./regexptest.php 239 lines Parsed ok!
> >> 7: ./postprocess.php 21 lines Parsed ok!
> >> 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
> >> ...
> >>
> >> Ie, it tells me it could parse all files except the one you gave me
> >> (which i  saved as testcode.php when i saved it from the browser)
> >>
> >> I can then click on 'Did not parse ok' which is a link.
> >>
> >> Gubed will now show the code in modified (parsed) and unmodified
> >> versions side  by side as well as tell you what line it fails on.
> >> Sometimes the line is not  exact, since a parse error from gubed can
> >> result in a syntax error further  down (just like php give you the wrong
> >> line number sometimes).
> >>
> >> I find the line it tells me and compare the parsed code to the original
> >> and  figure out what went wrong, this time it was very easy...
> >>
> >> Anyway, you can always send unparsable files if you dont want to do this
> >> work  yourself.
> >> You're also encouraged to do the "Start scanning entire system
> >> (*nix/Linux  only)" on regexptest.php if you can and see if you have
> >> other unparsable  files...
> >>
> >> Thanks for reporting the bug and let me know if it works better now!
> >>
> >> cheers
> >> /Linus
> >>
> >> On Wednesday 06 July 2005 00.42, Iassen Hristov wrote:
> >>> I am trying to debug the OWL project.
> >>> <http://sourceforge.net/projects/owl/>
> >>>
> >>> It gives me
> >>>
> >>> 18:38:06: Warning: Parsed failed for file
> >>> "C:\apache2triad\htdocs\owl\lib\owl.lib.php", please verify that it
> >>> does not contain errors!
> >>>
> >>> The source for this file can be obtained from here:
> >>> <http://cvs.sourceforge.net/viewcvs.py/owl/owl-0.80/lib/owl.lib.php?r1=
> >>>1 .53
> >>>
> >>>
> >>> I tried to figure out where the problem can be and I don't much
> >>> understand the output of the develop/regexptest.php
> >>>
> >>> How do I figure out where is the problem with the parser?
> >>>
> >>> Any hint/help would be appreciated.
> >>>
> >>> ---
> >>> Iassen Hristov
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------
> >>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> >>> from IBM. Find simple to follow Roadmaps, straightforward articles,
> >>> informative Webcasts and more! Get everything you need to get up to
> >>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> >>> _______________________________________________
> >>> Gubed-devel mailing list
> >>> Gub...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/gubed-devel
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Gubed-devel mailing list
> > Gub...@li...
> > https://lists.sourceforge.net/lists/listinfo/gubed-devel
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

Re: [gbd-dev] Parsing error

[Iassen H. <ih...@da...>]

Never mind the previous post.
I had a mistake in the modification for the GET I did.
It works now.
Thanks a million.

For the record the problem seems to be on the line
$dNow = $sql->now();

Apparently PHP blows up on this when used with MSSql. Now need to figure
out why and fix it.

Thanks again for your help.

--On Wednesday, July 06, 2005 12:46 -0400 Iassen Hristov
<ih...@da...> wrote:

> Thank you.
> Now I can debug. However I need one clarification:
> 
> How do I debug a page that expects POST data as input?
> I could not find an example of how to do this.
> Or am I way off target here and I am supposed to be debugging in some
> completely different way?
> 
> Right now I can debug trough the index.php, but at the end it sends me to
> the same page (in the browser), because I need to input user name and
> password. I tried modifying the page to use GET (instead of POST) and
> provide the user name and password in the params, but it does not seem to
> be passing them.
> 
> In other words I provide
> /index.php?login=1&loginname=admin&password=admin
> 
> As the input in the StartSession page.
> <http://localhost/gubed/StartSession.php>
> 
> BTW: The problem I am trying to debug is this:
> I installed OWL on a Windows computer. It works fine when hitting a
> PostgreSQL database. However when I change it to use MSSql instead of
> Postgre I can't login. I traced the SQL statements it sends to the server
> and it seems fine up to a certain point. There are no errors whatsoever,
> but then it just finishes and sends me again to the login page. I suspect
> there is some kind of subtle error in the invoking code that somehow
> manifests itself only in the mssql library (or the returned result is
> somehow different and that messes it up).
> 
> 
> --On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
> wrote:
> 
>> 
>> Hi!
>> 
>> It was a while ago since a parsing error was reported... 
>> Replace your GubedParserTokenizer.php file with the attached one and it
>> should  work better.
>> 
>> About regexptest:
>> I took the file you sent me and put it on my computer, in the dir 
>> "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
>> 
>> Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
>> where  i put the file)
>> 
>> Then when i click "search" i get:
>> 
>> ...
>> 1: ./testcode.php 3837 lines T_ARRAY: 'array' 
>>    ***   Did not parse ok!   ***
>> 2: ./regexptestcode.php 375 lines Parsed ok!
>> 3: ./diffdisplay.php 123 lines Parsed ok!
>> 4: ./index.php 26 lines Parsed ok!
>> 5: ./postprocessdiff.php 68 lines Parsed ok!
>> 6: ./regexptest.php 239 lines Parsed ok!
>> 7: ./postprocess.php 21 lines Parsed ok!
>> 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
>> ...
>> 
>> Ie, it tells me it could parse all files except the one you gave me
>> (which i  saved as testcode.php when i saved it from the browser)
>> 
>> I can then click on 'Did not parse ok' which is a link.
>> 
>> Gubed will now show the code in modified (parsed) and unmodified versions
>> side  by side as well as tell you what line it fails on. Sometimes the
>> line is not  exact, since a parse error from gubed can result in a syntax
>> error further  down (just like php give you the wrong line number
>> sometimes).
>> 
>> I find the line it tells me and compare the parsed code to the original
>> and  figure out what went wrong, this time it was very easy...
>> 
>> Anyway, you can always send unparsable files if you dont want to do this
>> work  yourself.
>> You're also encouraged to do the "Start scanning entire system
>> (*nix/Linux  only)" on regexptest.php if you can and see if you have
>> other unparsable  files...
>> 
>> Thanks for reporting the bug and let me know if it works better now!
>> 
>> cheers
>> /Linus
>> 
>> On Wednesday 06 July 2005 00.42, Iassen Hristov wrote:
>>> I am trying to debug the OWL project.
>>> <http://sourceforge.net/projects/owl/>
>>> 
>>> It gives me
>>> 
>>> 18:38:06: Warning: Parsed failed for file
>>> "C:\apache2triad\htdocs\owl\lib\owl.lib.php", please verify that it does
>>> not contain errors!
>>> 
>>> The source for this file can be obtained from here:
>>> <http://cvs.sourceforge.net/viewcvs.py/owl/owl-0.80/lib/owl.lib.php?r1=1
>>> .53
>>>> 
>>> 
>>> I tried to figure out where the problem can be and I don't much
>>> understand the output of the develop/regexptest.php
>>> 
>>> How do I figure out where is the problem with the parser?
>>> 
>>> Any hint/help would be appreciated.
>>> 
>>> ---
>>> Iassen Hristov
>>> 
>>> 
>>> 
>>> -------------------------------------------------------
>>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>>> informative Webcasts and more! Get everything you need to get up to
>>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>> _______________________________________________
>>> Gubed-devel mailing list
>>> Gub...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gubed-devel
>> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

Re: [gbd-dev] Parsing error

[Iassen H. <ih...@da...>]

Thank you.
Now I can debug. However I need one clarification:

How do I debug a page that expects POST data as input?
I could not find an example of how to do this.
Or am I way off target here and I am supposed to be debugging in some
completely different way?

Right now I can debug trough the index.php, but at the end it sends me to
the same page (in the browser), because I need to input user name and
password. I tried modifying the page to use GET (instead of POST) and
provide the user name and password in the params, but it does not seem to
be passing them.

In other words I provide
/index.php?login=1&loginname=admin&password=admin

As the input in the StartSession page.
<http://localhost/gubed/StartSession.php>

BTW: The problem I am trying to debug is this:
I installed OWL on a Windows computer. It works fine when hitting a
PostgreSQL database. However when I change it to use MSSql instead of
Postgre I can't login. I traced the SQL statements it sends to the server
and it seems fine up to a certain point. There are no errors whatsoever,
but then it just finishes and sends me again to the login page. I suspect
there is some kind of subtle error in the invoking code that somehow
manifests itself only in the mssql library (or the returned result is
somehow different and that messes it up).


--On Wednesday, July 06, 2005 06:09 +0200 Linus McCabe <Li...@mc...>
wrote:

> 
> Hi!
> 
> It was a while ago since a parsing error was reported... 
> Replace your GubedParserTokenizer.php file with the attached one and it
> should  work better.
> 
> About regexptest:
> I took the file you sent me and put it on my computer, in the dir 
> "Gubed/ServerScripts/develop" to be precise, but it can be anywhere.
> 
> Then I enter ./ in 'specify path' on the regexptest page. (ie, the path
> where  i put the file)
> 
> Then when i click "search" i get:
> 
> ...
> 1: ./testcode.php 3837 lines T_ARRAY: 'array' 
>    ***   Did not parse ok!   ***
> 2: ./regexptestcode.php 375 lines Parsed ok!
> 3: ./diffdisplay.php 123 lines Parsed ok!
> 4: ./index.php 26 lines Parsed ok!
> 5: ./postprocessdiff.php 68 lines Parsed ok!
> 6: ./regexptest.php 239 lines Parsed ok!
> 7: ./postprocess.php 21 lines Parsed ok!
> 8: ./regexptestcode_handmade.php 381 lines Original file did not parse
> ...
> 
> Ie, it tells me it could parse all files except the one you gave me
> (which i  saved as testcode.php when i saved it from the browser)
> 
> I can then click on 'Did not parse ok' which is a link.
> 
> Gubed will now show the code in modified (parsed) and unmodified versions
> side  by side as well as tell you what line it fails on. Sometimes the
> line is not  exact, since a parse error from gubed can result in a syntax
> error further  down (just like php give you the wrong line number
> sometimes).
> 
> I find the line it tells me and compare the parsed code to the original
> and  figure out what went wrong, this time it was very easy...
> 
> Anyway, you can always send unparsable files if you dont want to do this
> work  yourself.
> You're also encouraged to do the "Start scanning entire system
> (*nix/Linux  only)" on regexptest.php if you can and see if you have
> other unparsable  files...
> 
> Thanks for reporting the bug and let me know if it works better now!
> 
> cheers
> /Linus
> 
> On Wednesday 06 July 2005 00.42, Iassen Hristov wrote:
>> I am trying to debug the OWL project.
>> <http://sourceforge.net/projects/owl/>
>> 
>> It gives me
>> 
>> 18:38:06: Warning: Parsed failed for file
>> "C:\apache2triad\htdocs\owl\lib\owl.lib.php", please verify that it does
>> not contain errors!
>> 
>> The source for this file can be obtained from here:
>> <http://cvs.sourceforge.net/viewcvs.py/owl/owl-0.80/lib/owl.lib.php?r1=1
>> .53
>>> 
>> 
>> I tried to figure out where the problem can be and I don't much
>> understand the output of the develop/regexptest.php
>> 
>> How do I figure out where is the problem with the parser?
>> 
>> Any hint/help would be appreciated.
>> 
>> ---
>> Iassen Hristov
>> 
>> 
>> 
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> Gubed-devel mailing list
>> Gub...@li...
>> https://lists.sourceforge.net/lists/listinfo/gubed-devel
> 

Re: [gbd-dev] Parsing error

[Linus M. <Li...@mc...>]

Hi!

It was a while ago since a parsing error was reported... 
Replace your GubedParserTokenizer.php file with the attached one and it should 
work better.

About regexptest:
I took the file you sent me and put it on my computer, in the dir 
"Gubed/ServerScripts/develop" to be precise, but it can be anywhere.

Then I enter ./ in 'specify path' on the regexptest page. (ie, the path where 
i put the file)

Then when i click "search" i get:

...
1: ./testcode.php 3837 lines T_ARRAY: 'array' 
   ***   Did not parse ok!   ***
2: ./regexptestcode.php 375 lines Parsed ok!
3: ./diffdisplay.php 123 lines Parsed ok!
4: ./index.php 26 lines Parsed ok!
5: ./postprocessdiff.php 68 lines Parsed ok!
6: ./regexptest.php 239 lines Parsed ok!
7: ./postprocess.php 21 lines Parsed ok!
8: ./regexptestcode_handmade.php 381 lines Original file did not parse
...

Ie, it tells me it could parse all files except the one you gave me (which i 
saved as testcode.php when i saved it from the browser)

I can then click on 'Did not parse ok' which is a link.

Gubed will now show the code in modified (parsed) and unmodified versions side 
by side as well as tell you what line it fails on. Sometimes the line is not 
exact, since a parse error from gubed can result in a syntax error further 
down (just like php give you the wrong line number sometimes).

I find the line it tells me and compare the parsed code to the original and 
figure out what went wrong, this time it was very easy...

Anyway, you can always send unparsable files if you dont want to do this work 
yourself.
You're also encouraged to do the "Start scanning entire system (*nix/Linux 
only)" on regexptest.php if you can and see if you have other unparsable 
files...

Thanks for reporting the bug and let me know if it works better now!

cheers
/Linus

On Wednesday 06 July 2005 00.42, Iassen Hristov wrote:
> I am trying to debug the OWL project.
> <http://sourceforge.net/projects/owl/>
>
> It gives me
>
> 18:38:06: Warning: Parsed failed for file
> "C:\apache2triad\htdocs\owl\lib\owl.lib.php", please verify that it does
> not contain errors!
>
> The source for this file can be obtained from here:
> <http://cvs.sourceforge.net/viewcvs.py/owl/owl-0.80/lib/owl.lib.php?r1=1.53
>>
>
> I tried to figure out where the problem can be and I don't much understand
> the output of the develop/regexptest.php
>
> How do I figure out where is the problem with the parser?
>
> Any hint/help would be appreciated.
>
> ---
> Iassen Hristov
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

[gbd-dev] Parsing error

[Iassen H. <ih...@da...>]

I am trying to debug the OWL project.
<http://sourceforge.net/projects/owl/>

It gives me 

18:38:06: Warning: Parsed failed for file
"C:\apache2triad\htdocs\owl\lib\owl.lib.php", please verify that it does
not contain errors!

The source for this file can be obtained from here:
<http://cvs.sourceforge.net/viewcvs.py/owl/owl-0.80/lib/owl.lib.php?r1=1.53>

I tried to figure out where the problem can be and I don't much understand
the output of the develop/regexptest.php

How do I figure out where is the problem with the parser?

Any hint/help would be appreciated.

---
Iassen Hristov

[gbd-dev] Gubed 0.2.1

[Linus M. <Li...@mc...>]

Hello

I just released Gubed 0.2.1 for Quanta and I will release 0.2.1 standalone in 
a couple of days. 

This release is mainly to get some bugfixes out.

It does not include the recent i18n or localsettings changes. The former since 
there are currently no translations anyway (and the package scripts do not 
generate mo's yet) and the latter because it will be changed soon anyway due 
to the recently discussed changes in settings handling.

cheers

/Linus

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Brett S. <tec...@se...>]

Yes, I saw that wxGTK-devel was also available via yum on fedora, didn't
realize it was what Nick was looking for.

Assuming that /etc/yum.conf was replaced as described in the Fedora FAQ
link I emailed earlier, the command 'yum list' (preferably redirected
into a file for later viewing) will show all available packages.

So using Linux filters, this command would be relevant in this case:

yum list | grep 'wxGTK'

Then for each package that looks interesting:

yum install 'package_name'

for example:

yum install wxGTK-devel

Brett

On Sun, 3 Jul 2005 14:17:33 +0200, "Linus McCabe" <Li...@mc...>
said:
> 
> I think perhaps youll need to get the wxGTK-devel (or is it
> wxWidgets-devel?) 
> packages and preferably also packages for wxSTC.. I'm not very familiar
> with 
> fedora, so i dont know how to find packages easily..
> 
> (Brett, is there something similar to packages.debian.org for fedora/yum
> ?)
> 
> /Linus
> 
> 
> On Sunday 03 July 2005 13.57, Nick McCulloch wrote:
> > Brett,
> >
> > 1 small step forward.....
> >
> > Followed your instructions and installed wxGTK using yum and attempted
> > the "build" of the Gubed 0.2.0 Client again.
> >
> > Once more it fails as shown below. Where do I go from here? Should I
> > just give up and go back to MS Windows? Any other ideas?
> >
> > Nick
> >
> >
> > ./configure
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking build system type... i686-redhat-linux-gnu
> > checking host system type... i686-redhat-linux-gnu
> > checking for style of include used by make... GNU
> > checking for gcc... gcc
> > checking for C compiler default output file name... a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for suffix of executables...
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether gcc accepts -g... yes
> > checking for gcc option to accept ANSI C... none needed
> > checking dependency style of gcc... gcc3
> > checking for a sed that does not truncate output... /bin/sed
> > checking for egrep... grep -E
> > checking for ld used by gcc... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking for /usr/bin/ld option to reload object files... -r
> > checking for BSD-compatible nm... /usr/bin/nm -B
> > checking whether ln -s works... yes
> > checking how to recognise dependent libraries... pass_all
> > checking how to run the C preprocessor... gcc -E
> > checking for ANSI C header files... yes
> > checking for sys/types.h... yes
> > checking for sys/stat.h... yes
> > checking for stdlib.h... yes
> > checking for string.h... yes
> > checking for memory.h... yes
> > checking for strings.h... yes
> > checking for inttypes.h... yes
> > checking for stdint.h... yes
> > checking for unistd.h... yes
> > checking dlfcn.h usability... yes
> > checking dlfcn.h presence... yes
> > checking for dlfcn.h... yes
> > checking for g++... g++
> > checking whether we are using the GNU C++ compiler... yes
> > checking whether g++ accepts -g... yes
> > checking dependency style of g++... gcc3
> > checking how to run the C++ preprocessor... g++ -E
> > checking for g77... g77
> > checking whether we are using the GNU Fortran 77 compiler... yes
> > checking whether g77 accepts -g... yes
> > checking the maximum length of command line arguments... 32768
> > checking command to parse /usr/bin/nm -B output from gcc object... ok
> > checking for objdir... .libs
> > checking for ar... ar
> > checking for ranlib... ranlib
> > checking for strip... strip
> > checking if gcc static flag  works... yes
> > checking if gcc supports -fno-rtti -fno-exceptions... no
> > checking for gcc option to produce PIC... -fPIC
> > checking if gcc PIC flag -fPIC works... yes
> > checking if gcc supports -c -o file.o... yes
> > checking whether the gcc linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking whether -lc should be explicitly linked in... no
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... yes
> > configure: creating libtool
> > appending configuration tag "CXX" to libtool
> > checking for ld used by g++... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking whether the g++ linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking for g++ option to produce PIC... -fPIC
> > checking if g++ PIC flag -fPIC works... yes
> > checking if g++ supports -c -o file.o... yes
> > checking whether the g++ linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > appending configuration tag "F77" to libtool
> > checking if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... yes
> > checking for g77 option to produce PIC... -fPIC
> > checking if g77 PIC flag -fPIC works... yes
> > checking if g77 supports -c -o file.o... yes
> > checking whether the g77 linker (/usr/bin/ld) supports shared
> > libraries... yes
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > checking whether stripping libraries is possible... yes
> > checking whether we are using the GNU C++ compiler... (cached) yes
> > checking whether g++ accepts -g... (cached) yes
> > checking dependency style of g++... (cached) gcc3
> > checking wxWindows version... ./configure: line 19606: wx-config:
> > command not found
> > not found
> > configure: error: wxWindows is required. Try --with-wx-config.
> >
> > On Sun, 2005-07-03 at 07:07 -0400, Brett Serkez wrote:
> > > Nick,
> > >
> > > The widgets are in Fedora extras.  This link describes how to setup for
> > > extras and more:
> > >
> > > http://fcp.homelinux.org/modules/smartfaq/faq.php?faqid=110
> > >
> > > Then all you need to do is:
> > >
> > > yum install wxGTK
> > >
> > > Brett
> > >
> > > On Sun, 03 Jul 2005 09:28:31 +0100, "Nick McCulloch"
> > >
> > > <nmc...@bl...> said:
> > > > Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> > > > while Quanta just hung up completely! I had to logout-login to kill the
> > > > quanta process.
> > > >
> > > > So... I downloaded the Gubed 0.2.0 traball and tried to build the
> > > > client. Seems it needs wxwindows which isn't part of RC3. Where do I
> > > > find the rpm for that one?
> > > >
> > > > linux just doesn't make life simple for newcomers to the OS !!!!
> > > >
> > > > Nick
> > > >
> > > > On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > > > > Nick,
> > > > >
> > > > > I've been using Linux since almost the first Redhat release and
> > > > > closely follow several distros.  Fedora is a very good distro for
> > > > > many reasons, but I'm not sure FC4 is the best place to start.  I'm
> > > > > on the Fedora mailing list and while I think it will be a blow away
> > > > > release, FC3 with all patches is a more stable environment.  The
> > > > > standard FC3 environment:
> > > > >
> > > > > Gubed Version   0.2.0
> > > > > Protocol Version        0.0.12
> > > > > PHP Version     4.3.11
> > > > > Tokenizer       Yes
> > > > > Backtrace       Yes
> > > > > Server  Apache/2.0.52 (Fedora)
> > > > >
> > > > > I know Gubed works fine in this environment.  My issues revolved
> > > > > around multiple users running out of their public_html directories,
> > > > > which you can read about in existing posts on the mailing list, I was
> > > > > specific about how to work around the issues.
> > > > >
> > > > > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > > > > kernel' from a command login before logging into the user interface
> > > > > the first time.  The installation of the kernel requires a reboot.
> > > > > This takes a while (I usually let it run over night), but once done,
> > > > > the release is stable and reliable (and fast on old equipment).  I
> > > > > have a couple of vintage mid-90 system running this environment, with
> > > > > multiple users, everything is stable and fast.
> > > > >
> > > > > I'll be experimenting with FC4 in a few weeks, once I see the number
> > > > > of issues drop on their mailing list.  The biggest issue at this
> > > > > point is the kernel is bloated, it needs triming, but I also think
> > > > > fair adjustments are still being made to the overall environment.
> > > > >
> > > > > Brett
> > > > >
> > > > > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> > > > >
> > > > > <nmc...@bl...> said:
> > > > > > Hi Brett,
> > > > > >
> > > > > > Thanks for the reply. I'm running Fedora RC4 which has PHP5
> > > > > > included. I'm afraid I'm not very "clued up" on linux as this is
> > > > > > the first time I've stuck with a linux distro for more than a
> > > > > > couple of weeks.
> > > > > >
> > > > > > I may try the Gubed client shortly but I haven't had much success
> > > > > > so far when it comes to installing from source/tarballs.
> > > > > >
> > > > > > Maybe Linus can tell us if there are issues running with PHP5?
> > > > > >
> > > > > > > Nick,
> > > > > > >
> > > > > > > I see you are running php V5.  It looks like you might be running
> > > > > > > Fedora 3?
> > > > > > >
> > > > > > > I've been using Gubed on FC3 with all patches for some time.  I
> > > > > > > happen to install php5 (V5.1.0b2) recently and am just starting
> > > > > > > to use it.  So far I've been able to debug, but I cannot remove
> > > > > > > php V4.3.11 just yet.
> > > > > > >
> > > > > > > How did you install php5?  I was unable to find any rpms and had
> > > > > > > to build from source.
> > > > > > >
> > > > > > > It looks to me as if their *might* be issues launching Gubed from
> > > > > > > StartSession.php with php5, but with my setup it is not clear yet
> > > > > > > if it is Gubed or my environment.  That is it seems to launch my
> > > > > > > php5 scripts as php4, attempting to force StartSession.php to run
> > > > > > > under php5 is problematic with my environment as it is.
> > > > > > >
> > > > > > > Have your tried the Gubed debug client just to see if it will
> > > > > > > work? Have you tried regressing to php4 to see if it will work
> > > > > > > with Quanta?
> > > > > > >
> > > > > > > Brett
> > > > > > >
> > > > > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > > > > >
> > > > > > > <nmc...@bl...> said:
> > > > > > > > Hi Linus,
> > > > > > > > I hope the following info helps. All I really want to do is
> > > > > > > > web/php with debug. All this other hassle just drives me crazy
> > > > > > > > :-)
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Nick
> > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > I'm not very familiar with Fedora, but I know there's been
> > > > > > > > > reports of strange behaviour with Fedora and Quanta on the
> > > > > > > > > Quanta mailinglist.
> > > > > > > > >
> > > > > > > > > It seems really strange that it works to telnet to 8016, but
> > > > > > > > > not to connect with gubed. When you connect with telnet, do
> > > > > > > > > you get some text information?
> > > > > > > > >
> > > > > > > > > Ill need a bit more of information:
> > > > > > > > > From what I understand you run both the webserver and quanta
> > > > > > > > > on the same box?
> > > > > > > >
> > > > > > > > Thats correct. apache is a "straight from the cd" setup. No
> > > > > > > > special stuff configured here.
> > > > > > > >
> > > > > > > > > When you look at the index page of Gubed, there is a link to
> > > > > > > > > a 'debug info page'. Could you look at that page and copy the
> > > > > > > > > debug information in your next mail?
> > > > > > > >
> > > > > > > > from the debug page:
> > > > > > > > Debug info
> > > > > > > > If you wish to submit a support or bug request, please include
> > > > > > > > the output of this page in your request. It containts the most
> > > > > > > > common information the developers will need to help you.
> > > > > > > >
> > > > > > > >               Property
> > > > > > > >                Value
> > > > > > > > Gubed Version
> > > > > > > > 0.1.4
> > > > > > > > Protocol Version
> > > > > > > > 0.0.11
> > > > > > > > PHP Version
> > > > > > > > 5.0.4
> > > > > > > > Tokenizer
> > > > > > > > Yes
> > > > > > > > Backtrace
> > > > > > > > Yes
> > > > > > > > Server
> > > > > > > > Apache/2.0.54 (Fedora)
> > > > > > > >
> > > > > > > > > When you connect with telnet, do you get any text from
> > > > > > > > > quanta?
> > > > > > > >
> > > > > > > > There is one line with "wait" then a couple of blank lines and
> > > > > > > > thats all. Exiting from Quanta then shows a "die" line.
> > > > > > > >
> > > > > > > > > I send this also to the gubed mailinglist, in case someone
> > > > > > > > > else has ideas
> > > > > > > > >
> > > > > > > > > /Linus
> > > > > > > > >
> > > > > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > > > > Hi,
> > > > > > > > > >
> > > > > > > > > > I'm completely new to linux and all I want to do is develop
> > > > > > > > > > some web stuff with php/mysql. But, I've been trying to get
> > > > > > > > > > the debugger to work with Quanta 3.4 and I keep getting
> > > > > > > > > > "Unable to connect to debug server on 127.0.0.1:8016."
> > > > > > > > > >
> > > > > > > > > > Now, I know the the debug server is listening by telnetting
> > > > > > > > > > to port 8016 on localhost when quanta is running so I dont
> > > > > > > > > > understand why debug doesnt work for me. Its just driving
> > > > > > > > > > me nuts!!!!
> > > > > > > > > >
> > > > > > > > > > I'm running "out of the box" Fedora RC4 and I followed the
> > > > > > > > > > tutorial at
> > > > > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > > > > >
> > > > > > > > > > I'm getting really frustrated by how hard it is to get
> > > > > > > > > > anything to work with linux. Can you help?
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Nick
> > > > > > > >
> > > > > > > > -------------------------------------------------------
> > > > > > > > SF.Net email is sponsored by: Discover Easy Linux Migration
> > > > > > > > Strategies from IBM. Find simple to follow Roadmaps,
> > > > > > > > straightforward articles, informative Webcasts and more! Get
> > > > > > > > everything you need to get up to speed, fast.
> > > > > > > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > > > > _______________________________________________
> > > > > > > > Gubed-devel mailing list
> > > > > > > > Gub...@li...
> > > > > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > > > > >
> > > > > > > -------------------------------------
> > > > > > > Brett C. Serkez, Technical Trainer
> > > > >
> > > > > -------------------------------------
> > > > > Brett C. Serkez, Technical Trainer
> > >
> > > -------------------------------------
> > > Brett C. Serkez, Technical Trainer
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Gubed-devel mailing list
> > Gub...@li...
> > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Linus M. <Li...@mc...>]

I think perhaps youll need to get the wxGTK-devel (or is it wxWidgets-devel?) 
packages and preferably also packages for wxSTC.. I'm not very familiar with 
fedora, so i dont know how to find packages easily..

(Brett, is there something similar to packages.debian.org for fedora/yum ?)

/Linus


On Sunday 03 July 2005 13.57, Nick McCulloch wrote:
> Brett,
>
> 1 small step forward.....
>
> Followed your instructions and installed wxGTK using yum and attempted
> the "build" of the Gubed 0.2.0 Client again.
>
> Once more it fails as shown below. Where do I go from here? Should I
> just give up and go back to MS Windows? Any other ideas?
>
> Nick
>
>
> ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking build system type... i686-redhat-linux-gnu
> checking host system type... i686-redhat-linux-gnu
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking dependency style of gcc... gcc3
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag  works... yes
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld) supports shared
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works... yes
> checking if g77 supports -c -o file.o... yes
> checking whether the g77 linker (/usr/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking whether we are using the GNU C++ compiler... (cached) yes
> checking whether g++ accepts -g... (cached) yes
> checking dependency style of g++... (cached) gcc3
> checking wxWindows version... ./configure: line 19606: wx-config:
> command not found
> not found
> configure: error: wxWindows is required. Try --with-wx-config.
>
> On Sun, 2005-07-03 at 07:07 -0400, Brett Serkez wrote:
> > Nick,
> >
> > The widgets are in Fedora extras.  This link describes how to setup for
> > extras and more:
> >
> > http://fcp.homelinux.org/modules/smartfaq/faq.php?faqid=110
> >
> > Then all you need to do is:
> >
> > yum install wxGTK
> >
> > Brett
> >
> > On Sun, 03 Jul 2005 09:28:31 +0100, "Nick McCulloch"
> >
> > <nmc...@bl...> said:
> > > Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> > > while Quanta just hung up completely! I had to logout-login to kill the
> > > quanta process.
> > >
> > > So... I downloaded the Gubed 0.2.0 traball and tried to build the
> > > client. Seems it needs wxwindows which isn't part of RC3. Where do I
> > > find the rpm for that one?
> > >
> > > linux just doesn't make life simple for newcomers to the OS !!!!
> > >
> > > Nick
> > >
> > > On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > > > Nick,
> > > >
> > > > I've been using Linux since almost the first Redhat release and
> > > > closely follow several distros.  Fedora is a very good distro for
> > > > many reasons, but I'm not sure FC4 is the best place to start.  I'm
> > > > on the Fedora mailing list and while I think it will be a blow away
> > > > release, FC3 with all patches is a more stable environment.  The
> > > > standard FC3 environment:
> > > >
> > > > Gubed Version   0.2.0
> > > > Protocol Version        0.0.12
> > > > PHP Version     4.3.11
> > > > Tokenizer       Yes
> > > > Backtrace       Yes
> > > > Server  Apache/2.0.52 (Fedora)
> > > >
> > > > I know Gubed works fine in this environment.  My issues revolved
> > > > around multiple users running out of their public_html directories,
> > > > which you can read about in existing posts on the mailing list, I was
> > > > specific about how to work around the issues.
> > > >
> > > > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > > > kernel' from a command login before logging into the user interface
> > > > the first time.  The installation of the kernel requires a reboot.
> > > > This takes a while (I usually let it run over night), but once done,
> > > > the release is stable and reliable (and fast on old equipment).  I
> > > > have a couple of vintage mid-90 system running this environment, with
> > > > multiple users, everything is stable and fast.
> > > >
> > > > I'll be experimenting with FC4 in a few weeks, once I see the number
> > > > of issues drop on their mailing list.  The biggest issue at this
> > > > point is the kernel is bloated, it needs triming, but I also think
> > > > fair adjustments are still being made to the overall environment.
> > > >
> > > > Brett
> > > >
> > > > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> > > >
> > > > <nmc...@bl...> said:
> > > > > Hi Brett,
> > > > >
> > > > > Thanks for the reply. I'm running Fedora RC4 which has PHP5
> > > > > included. I'm afraid I'm not very "clued up" on linux as this is
> > > > > the first time I've stuck with a linux distro for more than a
> > > > > couple of weeks.
> > > > >
> > > > > I may try the Gubed client shortly but I haven't had much success
> > > > > so far when it comes to installing from source/tarballs.
> > > > >
> > > > > Maybe Linus can tell us if there are issues running with PHP5?
> > > > >
> > > > > > Nick,
> > > > > >
> > > > > > I see you are running php V5.  It looks like you might be running
> > > > > > Fedora 3?
> > > > > >
> > > > > > I've been using Gubed on FC3 with all patches for some time.  I
> > > > > > happen to install php5 (V5.1.0b2) recently and am just starting
> > > > > > to use it.  So far I've been able to debug, but I cannot remove
> > > > > > php V4.3.11 just yet.
> > > > > >
> > > > > > How did you install php5?  I was unable to find any rpms and had
> > > > > > to build from source.
> > > > > >
> > > > > > It looks to me as if their *might* be issues launching Gubed from
> > > > > > StartSession.php with php5, but with my setup it is not clear yet
> > > > > > if it is Gubed or my environment.  That is it seems to launch my
> > > > > > php5 scripts as php4, attempting to force StartSession.php to run
> > > > > > under php5 is problematic with my environment as it is.
> > > > > >
> > > > > > Have your tried the Gubed debug client just to see if it will
> > > > > > work? Have you tried regressing to php4 to see if it will work
> > > > > > with Quanta?
> > > > > >
> > > > > > Brett
> > > > > >
> > > > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > > > >
> > > > > > <nmc...@bl...> said:
> > > > > > > Hi Linus,
> > > > > > > I hope the following info helps. All I really want to do is
> > > > > > > web/php with debug. All this other hassle just drives me crazy
> > > > > > > :-)
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nick
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I'm not very familiar with Fedora, but I know there's been
> > > > > > > > reports of strange behaviour with Fedora and Quanta on the
> > > > > > > > Quanta mailinglist.
> > > > > > > >
> > > > > > > > It seems really strange that it works to telnet to 8016, but
> > > > > > > > not to connect with gubed. When you connect with telnet, do
> > > > > > > > you get some text information?
> > > > > > > >
> > > > > > > > Ill need a bit more of information:
> > > > > > > > From what I understand you run both the webserver and quanta
> > > > > > > > on the same box?
> > > > > > >
> > > > > > > Thats correct. apache is a "straight from the cd" setup. No
> > > > > > > special stuff configured here.
> > > > > > >
> > > > > > > > When you look at the index page of Gubed, there is a link to
> > > > > > > > a 'debug info page'. Could you look at that page and copy the
> > > > > > > > debug information in your next mail?
> > > > > > >
> > > > > > > from the debug page:
> > > > > > > Debug info
> > > > > > > If you wish to submit a support or bug request, please include
> > > > > > > the output of this page in your request. It containts the most
> > > > > > > common information the developers will need to help you.
> > > > > > >
> > > > > > >               Property
> > > > > > >                Value
> > > > > > > Gubed Version
> > > > > > > 0.1.4
> > > > > > > Protocol Version
> > > > > > > 0.0.11
> > > > > > > PHP Version
> > > > > > > 5.0.4
> > > > > > > Tokenizer
> > > > > > > Yes
> > > > > > > Backtrace
> > > > > > > Yes
> > > > > > > Server
> > > > > > > Apache/2.0.54 (Fedora)
> > > > > > >
> > > > > > > > When you connect with telnet, do you get any text from
> > > > > > > > quanta?
> > > > > > >
> > > > > > > There is one line with "wait" then a couple of blank lines and
> > > > > > > thats all. Exiting from Quanta then shows a "die" line.
> > > > > > >
> > > > > > > > I send this also to the gubed mailinglist, in case someone
> > > > > > > > else has ideas
> > > > > > > >
> > > > > > > > /Linus
> > > > > > > >
> > > > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I'm completely new to linux and all I want to do is develop
> > > > > > > > > some web stuff with php/mysql. But, I've been trying to get
> > > > > > > > > the debugger to work with Quanta 3.4 and I keep getting
> > > > > > > > > "Unable to connect to debug server on 127.0.0.1:8016."
> > > > > > > > >
> > > > > > > > > Now, I know the the debug server is listening by telnetting
> > > > > > > > > to port 8016 on localhost when quanta is running so I dont
> > > > > > > > > understand why debug doesnt work for me. Its just driving
> > > > > > > > > me nuts!!!!
> > > > > > > > >
> > > > > > > > > I'm running "out of the box" Fedora RC4 and I followed the
> > > > > > > > > tutorial at
> > > > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > > > >
> > > > > > > > > I'm getting really frustrated by how hard it is to get
> > > > > > > > > anything to work with linux. Can you help?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Nick
> > > > > > >
> > > > > > > -------------------------------------------------------
> > > > > > > SF.Net email is sponsored by: Discover Easy Linux Migration
> > > > > > > Strategies from IBM. Find simple to follow Roadmaps,
> > > > > > > straightforward articles, informative Webcasts and more! Get
> > > > > > > everything you need to get up to speed, fast.
> > > > > > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > > > _______________________________________________
> > > > > > > Gubed-devel mailing list
> > > > > > > Gub...@li...
> > > > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > > > >
> > > > > > -------------------------------------
> > > > > > Brett C. Serkez, Technical Trainer
> > > >
> > > > -------------------------------------
> > > > Brett C. Serkez, Technical Trainer
> >
> > -------------------------------------
> > Brett C. Serkez, Technical Trainer
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Brett S. <tec...@se...>]

Nick,

Well I wouldn't recommend anybody go back to WinDoze.  That being said,
I still run my desktop as WinDoze and and been running the Gubed
debugger on WinDoze and web environments on both Linux and WinDoze.

I'd follow Linus's pointer to the wx widget rpms and install them
directly.  The rpms installer should keep you out of trouble and not let
incompatible combinations be installed.

Yes, the Linux/UNIX world is frustrating at first, but so is any other
new environment.  Once you get used to it, it is difficult to go back to
'other' environments.  Sticking with it will pay rewards, hang in their,
everyone needs to pay their dues.  :-)

Brett

On Sun, 03 Jul 2005 12:57:12 +0100, "Nick McCulloch"
<nmc...@bl...> said:
> Brett,
> 
> 1 small step forward..... 
> 
> Followed your instructions and installed wxGTK using yum and attempted
> the "build" of the Gubed 0.2.0 Client again. 
> 
> Once more it fails as shown below. Where do I go from here? Should I
> just give up and go back to MS Windows? Any other ideas?
> 
> Nick
> 
> 
> ./configure 
> checking for a BSD-compatible install... /usr/bin/install -c 
> checking whether build environment is sane... yes 
> checking for gawk... gawk 
> checking whether make sets $(MAKE)... yes 
> checking build system type... i686-redhat-linux-gnu 
> checking host system type... i686-redhat-linux-gnu 
> checking for style of include used by make... GNU 
> checking for gcc... gcc 
> checking for C compiler default output file name... a.out 
> checking whether the C compiler works... yes 
> checking whether we are cross compiling... no 
> checking for suffix of executables... 
> checking for suffix of object files... o 
> checking whether we are using the GNU C compiler... yes 
> checking whether gcc accepts -g... yes 
> checking for gcc option to accept ANSI C... none needed 
> checking dependency style of gcc... gcc3 
> checking for a sed that does not truncate output... /bin/sed 
> checking for egrep... grep -E 
> checking for ld used by gcc... /usr/bin/ld 
> checking if the linker (/usr/bin/ld) is GNU ld... yes 
> checking for /usr/bin/ld option to reload object files... -r 
> checking for BSD-compatible nm... /usr/bin/nm -B 
> checking whether ln -s works... yes 
> checking how to recognise dependent libraries... pass_all 
> checking how to run the C preprocessor... gcc -E 
> checking for ANSI C header files... yes 
> checking for sys/types.h... yes 
> checking for sys/stat.h... yes 
> checking for stdlib.h... yes 
> checking for string.h... yes 
> checking for memory.h... yes 
> checking for strings.h... yes 
> checking for inttypes.h... yes 
> checking for stdint.h... yes 
> checking for unistd.h... yes 
> checking dlfcn.h usability... yes 
> checking dlfcn.h presence... yes 
> checking for dlfcn.h... yes 
> checking for g++... g++ 
> checking whether we are using the GNU C++ compiler... yes 
> checking whether g++ accepts -g... yes 
> checking dependency style of g++... gcc3 
> checking how to run the C++ preprocessor... g++ -E 
> checking for g77... g77 
> checking whether we are using the GNU Fortran 77 compiler... yes 
> checking whether g77 accepts -g... yes 
> checking the maximum length of command line arguments... 32768 
> checking command to parse /usr/bin/nm -B output from gcc object... ok 
> checking for objdir... .libs 
> checking for ar... ar 
> checking for ranlib... ranlib 
> checking for strip... strip 
> checking if gcc static flag  works... yes 
> checking if gcc supports -fno-rtti -fno-exceptions... no 
> checking for gcc option to produce PIC... -fPIC 
> checking if gcc PIC flag -fPIC works... yes 
> checking if gcc supports -c -o file.o... yes 
> checking whether the gcc linker (/usr/bin/ld) supports shared
> libraries... yes 
> checking whether -lc should be explicitly linked in... no 
> checking dynamic linker characteristics... GNU/Linux ld.so 
> checking how to hardcode library paths into programs... immediate 
> checking whether stripping libraries is possible... yes 
> checking if libtool supports shared libraries... yes 
> checking whether to build shared libraries... yes 
> checking whether to build static libraries... yes 
> configure: creating libtool 
> appending configuration tag "CXX" to libtool 
> checking for ld used by g++... /usr/bin/ld 
> checking if the linker (/usr/bin/ld) is GNU ld... yes 
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes 
> checking for g++ option to produce PIC... -fPIC 
> checking if g++ PIC flag -fPIC works... yes 
> checking if g++ supports -c -o file.o... yes 
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes 
> checking dynamic linker characteristics... GNU/Linux ld.so 
> checking how to hardcode library paths into programs... immediate 
> checking whether stripping libraries is possible... yes 
> appending configuration tag "F77" to libtool 
> checking if libtool supports shared libraries... yes 
> checking whether to build shared libraries... yes 
> checking whether to build static libraries... yes 
> checking for g77 option to produce PIC... -fPIC 
> checking if g77 PIC flag -fPIC works... yes 
> checking if g77 supports -c -o file.o... yes 
> checking whether the g77 linker (/usr/bin/ld) supports shared
> libraries... yes 
> checking dynamic linker characteristics... GNU/Linux ld.so 
> checking how to hardcode library paths into programs... immediate 
> checking whether stripping libraries is possible... yes 
> checking whether we are using the GNU C++ compiler... (cached) yes 
> checking whether g++ accepts -g... (cached) yes 
> checking dependency style of g++... (cached) gcc3 
> checking wxWindows version... ./configure: line 19606: wx-config:
> command not found 
> not found 
> configure: error: wxWindows is required. Try --with-wx-config. 
> 
> 
> On Sun, 2005-07-03 at 07:07 -0400, Brett Serkez wrote:
> > Nick,
> > 
> > The widgets are in Fedora extras.  This link describes how to setup for
> > extras and more:
> > 
> > http://fcp.homelinux.org/modules/smartfaq/faq.php?faqid=110
> > 
> > Then all you need to do is:
> > 
> > yum install wxGTK
> > 
> > Brett
> > 
> > On Sun, 03 Jul 2005 09:28:31 +0100, "Nick McCulloch"
> > <nmc...@bl...> said:
> > > Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> > > while Quanta just hung up completely! I had to logout-login to kill the
> > > quanta process.
> > > 
> > > So... I downloaded the Gubed 0.2.0 traball and tried to build the
> > > client. Seems it needs wxwindows which isn't part of RC3. Where do I
> > > find the rpm for that one?
> > > 
> > > linux just doesn't make life simple for newcomers to the OS !!!!
> > > 
> > > Nick
> > > On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > > > Nick,
> > > > 
> > > > I've been using Linux since almost the first Redhat release and closely
> > > > follow several distros.  Fedora is a very good distro for many reasons,
> > > > but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> > > > mailing list and while I think it will be a blow away release, FC3 with
> > > > all patches is a more stable environment.  The standard FC3 environment:
> > > > 
> > > > Gubed Version   0.2.0
> > > > Protocol Version        0.0.12
> > > > PHP Version     4.3.11
> > > > Tokenizer       Yes
> > > > Backtrace       Yes
> > > > Server  Apache/2.0.52 (Fedora)
> > > > 
> > > > I know Gubed works fine in this environment.  My issues revolved around
> > > > multiple users running out of their public_html directories, which you
> > > > can read about in existing posts on the mailing list, I was specific
> > > > about how to work around the issues.
> > > > 
> > > > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > > > kernel' from a command login before logging into the user interface the
> > > > first time.  The installation of the kernel requires a reboot. This
> > > > takes a while (I usually let it run over night), but once done, the
> > > > release is stable and reliable (and fast on old equipment).  I have a
> > > > couple of vintage mid-90 system running this environment, with multiple
> > > > users, everything is stable and fast.
> > > > 
> > > > I'll be experimenting with FC4 in a few weeks, once I see the number of
> > > > issues drop on their mailing list.  The biggest issue at this point is
> > > > the kernel is bloated, it needs triming, but I also think fair
> > > > adjustments are still being made to the overall environment.
> > > > 
> > > > Brett
> > > > 
> > > > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> > > > <nmc...@bl...> said:
> > > > > 
> > > > > Hi Brett,
> > > > > 
> > > > > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > > > > I'm afraid I'm not very "clued up" on linux as this is the first time
> > > > > I've stuck with a linux distro for more than a couple of weeks.
> > > > > 
> > > > > I may try the Gubed client shortly but I haven't had much success so far
> > > > > when it comes to installing from source/tarballs.
> > > > > 
> > > > > Maybe Linus can tell us if there are issues running with PHP5?
> > > > > 
> > > > > 
> > > > > > Nick,
> > > > > > 
> > > > > > I see you are running php V5.  It looks like you might be running Fedora
> > > > > > 3?
> > > > > > 
> > > > > > I've been using Gubed on FC3 with all patches for some time.  I happen
> > > > > > to install php5 (V5.1.0b2) recently and am just starting to use it.  So
> > > > > > far I've been able to debug, but I cannot remove php V4.3.11 just yet. 
> > > > > > 
> > > > > > How did you install php5?  I was unable to find any rpms and had to
> > > > > > build from source.
> > > > > > 
> > > > > > It looks to me as if their *might* be issues launching Gubed from
> > > > > > StartSession.php with php5, but with my setup it is not clear yet if it
> > > > > > is Gubed or my environment.  That is it seems to launch my php5 scripts
> > > > > > as php4, attempting to force StartSession.php to run under php5 is
> > > > > > problematic with my environment as it is.
> > > > > > 
> > > > > > Have your tried the Gubed debug client just to see if it will work? 
> > > > > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > > > > 
> > > > > > Brett
> > > > > > 
> > > > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > > > > <nmc...@bl...> said:
> > > > > > > Hi Linus,
> > > > > > > I hope the following info helps. All I really want to do is web/php with
> > > > > > > debug. All this other hassle just drives me crazy :-)
> > > > > > > 
> > > > > > > Regards,
> > > > > > > Nick
> > > > > > > 
> > > > > > > > Hello!
> > > > > > > > 
> > > > > > > > I'm not very familiar with Fedora, but I know there's been reports of strange 
> > > > > > > > behaviour with Fedora and Quanta on the Quanta mailinglist.
> > > > > > > > 
> > > > > > > > It seems really strange that it works to telnet to 8016, but not to connect 
> > > > > > > > with gubed. When you connect with telnet, do you get some text information?
> > > > > > > > 
> > > > > > > > Ill need a bit more of information:
> > > > > > > > From what I understand you run both the webserver and quanta on the same box?
> > > > > > > 
> > > > > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > > > > stuff configured here.
> > > > > > > 
> > > > > > > > 
> > > > > > > > When you look at the index page of Gubed, there is a link to a 'debug info 
> > > > > > > > page'. Could you look at that page and copy the debug information in your 
> > > > > > > > next mail?
> > > > > > > from the debug page:
> > > > > > > Debug info 
> > > > > > > If you wish to submit a support or bug request, please include the
> > > > > > > output of this page in your request. It containts the most common
> > > > > > > information the developers will need to help you. 
> > > > > > > 
> > > > > > >               Property
> > > > > > >                Value
> > > > > > > Gubed Version
> > > > > > > 0.1.4
> > > > > > > Protocol Version
> > > > > > > 0.0.11
> > > > > > > PHP Version
> > > > > > > 5.0.4
> > > > > > > Tokenizer
> > > > > > > Yes
> > > > > > > Backtrace
> > > > > > > Yes
> > > > > > > Server
> > > > > > > Apache/2.0.54 (Fedora)
> > > > > > > > 
> > > > > > > > When you connect with telnet, do you get any text from quanta?
> > > > > > > 
> > > > > > > There is one line with "wait" then a couple of blank lines and thats
> > > > > > > all. Exiting from Quanta then shows a "die" line.
> > > > > > > 
> > > > > > > > 
> > > > > > > > I send this also to the gubed mailinglist, in case someone else has ideas
> > > > > > > > 
> > > > > > > > /Linus
> > > > > > > > 
> > > > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I'm completely new to linux and all I want to do is develop some web
> > > > > > > > > stuff with php/mysql. But, I've been trying to get the debugger to work
> > > > > > > > > with Quanta 3.4 and I keep getting "Unable to connect to debug server on
> > > > > > > > > 127.0.0.1:8016."
> > > > > > > > >
> > > > > > > > > Now, I know the the debug server is listening by telnetting to port 8016
> > > > > > > > > on localhost when quanta is running so I dont understand why debug
> > > > > > > > > doesnt work for me. Its just driving me nuts!!!!
> > > > > > > > >
> > > > > > > > > I'm running "out of the box" Fedora RC4 and I followed the tutorial at
> > > > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > > > >
> > > > > > > > > I'm getting really frustrated by how hard it is to get anything to work
> > > > > > > > > with linux. Can you help?
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Nick
> > > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > -------------------------------------------------------
> > > > > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > > > > informative Webcasts and more! Get everything you need to get up to
> > > > > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > > > _______________________________________________
> > > > > > > Gubed-devel mailing list
> > > > > > > Gub...@li...
> > > > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > > > > -------------------------------------
> > > > > > Brett C. Serkez, Technical Trainer
> > > > > > 
> > > > > > 
> > > > > 
> > > > -------------------------------------
> > > > Brett C. Serkez, Technical Trainer
> > > > 
> > > > 
> > > 
> > -------------------------------------
> > Brett C. Serkez, Technical Trainer
> > 
> > 
> 
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Nick M. <nmc...@bl...>]

Brett,

1 small step forward..... 

Followed your instructions and installed wxGTK using yum and attempted
the "build" of the Gubed 0.2.0 Client again. 

Once more it fails as shown below. Where do I go from here? Should I
just give up and go back to MS Windows? Any other ideas?

Nick


./configure 
checking for a BSD-compatible install... /usr/bin/install -c 
checking whether build environment is sane... yes 
checking for gawk... gawk 
checking whether make sets $(MAKE)... yes 
checking build system type... i686-redhat-linux-gnu 
checking host system type... i686-redhat-linux-gnu 
checking for style of include used by make... GNU 
checking for gcc... gcc 
checking for C compiler default output file name... a.out 
checking whether the C compiler works... yes 
checking whether we are cross compiling... no 
checking for suffix of executables... 
checking for suffix of object files... o 
checking whether we are using the GNU C compiler... yes 
checking whether gcc accepts -g... yes 
checking for gcc option to accept ANSI C... none needed 
checking dependency style of gcc... gcc3 
checking for a sed that does not truncate output... /bin/sed 
checking for egrep... grep -E 
checking for ld used by gcc... /usr/bin/ld 
checking if the linker (/usr/bin/ld) is GNU ld... yes 
checking for /usr/bin/ld option to reload object files... -r 
checking for BSD-compatible nm... /usr/bin/nm -B 
checking whether ln -s works... yes 
checking how to recognise dependent libraries... pass_all 
checking how to run the C preprocessor... gcc -E 
checking for ANSI C header files... yes 
checking for sys/types.h... yes 
checking for sys/stat.h... yes 
checking for stdlib.h... yes 
checking for string.h... yes 
checking for memory.h... yes 
checking for strings.h... yes 
checking for inttypes.h... yes 
checking for stdint.h... yes 
checking for unistd.h... yes 
checking dlfcn.h usability... yes 
checking dlfcn.h presence... yes 
checking for dlfcn.h... yes 
checking for g++... g++ 
checking whether we are using the GNU C++ compiler... yes 
checking whether g++ accepts -g... yes 
checking dependency style of g++... gcc3 
checking how to run the C++ preprocessor... g++ -E 
checking for g77... g77 
checking whether we are using the GNU Fortran 77 compiler... yes 
checking whether g77 accepts -g... yes 
checking the maximum length of command line arguments... 32768 
checking command to parse /usr/bin/nm -B output from gcc object... ok 
checking for objdir... .libs 
checking for ar... ar 
checking for ranlib... ranlib 
checking for strip... strip 
checking if gcc static flag  works... yes 
checking if gcc supports -fno-rtti -fno-exceptions... no 
checking for gcc option to produce PIC... -fPIC 
checking if gcc PIC flag -fPIC works... yes 
checking if gcc supports -c -o file.o... yes 
checking whether the gcc linker (/usr/bin/ld) supports shared
libraries... yes 
checking whether -lc should be explicitly linked in... no 
checking dynamic linker characteristics... GNU/Linux ld.so 
checking how to hardcode library paths into programs... immediate 
checking whether stripping libraries is possible... yes 
checking if libtool supports shared libraries... yes 
checking whether to build shared libraries... yes 
checking whether to build static libraries... yes 
configure: creating libtool 
appending configuration tag "CXX" to libtool 
checking for ld used by g++... /usr/bin/ld 
checking if the linker (/usr/bin/ld) is GNU ld... yes 
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes 
checking for g++ option to produce PIC... -fPIC 
checking if g++ PIC flag -fPIC works... yes 
checking if g++ supports -c -o file.o... yes 
checking whether the g++ linker (/usr/bin/ld) supports shared
libraries... yes 
checking dynamic linker characteristics... GNU/Linux ld.so 
checking how to hardcode library paths into programs... immediate 
checking whether stripping libraries is possible... yes 
appending configuration tag "F77" to libtool 
checking if libtool supports shared libraries... yes 
checking whether to build shared libraries... yes 
checking whether to build static libraries... yes 
checking for g77 option to produce PIC... -fPIC 
checking if g77 PIC flag -fPIC works... yes 
checking if g77 supports -c -o file.o... yes 
checking whether the g77 linker (/usr/bin/ld) supports shared
libraries... yes 
checking dynamic linker characteristics... GNU/Linux ld.so 
checking how to hardcode library paths into programs... immediate 
checking whether stripping libraries is possible... yes 
checking whether we are using the GNU C++ compiler... (cached) yes 
checking whether g++ accepts -g... (cached) yes 
checking dependency style of g++... (cached) gcc3 
checking wxWindows version... ./configure: line 19606: wx-config:
command not found 
not found 
configure: error: wxWindows is required. Try --with-wx-config. 


On Sun, 2005-07-03 at 07:07 -0400, Brett Serkez wrote:
> Nick,
> 
> The widgets are in Fedora extras.  This link describes how to setup for
> extras and more:
> 
> http://fcp.homelinux.org/modules/smartfaq/faq.php?faqid=110
> 
> Then all you need to do is:
> 
> yum install wxGTK
> 
> Brett
> 
> On Sun, 03 Jul 2005 09:28:31 +0100, "Nick McCulloch"
> <nmc...@bl...> said:
> > Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> > while Quanta just hung up completely! I had to logout-login to kill the
> > quanta process.
> > 
> > So... I downloaded the Gubed 0.2.0 traball and tried to build the
> > client. Seems it needs wxwindows which isn't part of RC3. Where do I
> > find the rpm for that one?
> > 
> > linux just doesn't make life simple for newcomers to the OS !!!!
> > 
> > Nick
> > On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > > Nick,
> > > 
> > > I've been using Linux since almost the first Redhat release and closely
> > > follow several distros.  Fedora is a very good distro for many reasons,
> > > but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> > > mailing list and while I think it will be a blow away release, FC3 with
> > > all patches is a more stable environment.  The standard FC3 environment:
> > > 
> > > Gubed Version   0.2.0
> > > Protocol Version        0.0.12
> > > PHP Version     4.3.11
> > > Tokenizer       Yes
> > > Backtrace       Yes
> > > Server  Apache/2.0.52 (Fedora)
> > > 
> > > I know Gubed works fine in this environment.  My issues revolved around
> > > multiple users running out of their public_html directories, which you
> > > can read about in existing posts on the mailing list, I was specific
> > > about how to work around the issues.
> > > 
> > > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > > kernel' from a command login before logging into the user interface the
> > > first time.  The installation of the kernel requires a reboot. This
> > > takes a while (I usually let it run over night), but once done, the
> > > release is stable and reliable (and fast on old equipment).  I have a
> > > couple of vintage mid-90 system running this environment, with multiple
> > > users, everything is stable and fast.
> > > 
> > > I'll be experimenting with FC4 in a few weeks, once I see the number of
> > > issues drop on their mailing list.  The biggest issue at this point is
> > > the kernel is bloated, it needs triming, but I also think fair
> > > adjustments are still being made to the overall environment.
> > > 
> > > Brett
> > > 
> > > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> > > <nmc...@bl...> said:
> > > > 
> > > > Hi Brett,
> > > > 
> > > > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > > > I'm afraid I'm not very "clued up" on linux as this is the first time
> > > > I've stuck with a linux distro for more than a couple of weeks.
> > > > 
> > > > I may try the Gubed client shortly but I haven't had much success so far
> > > > when it comes to installing from source/tarballs.
> > > > 
> > > > Maybe Linus can tell us if there are issues running with PHP5?
> > > > 
> > > > 
> > > > > Nick,
> > > > > 
> > > > > I see you are running php V5.  It looks like you might be running Fedora
> > > > > 3?
> > > > > 
> > > > > I've been using Gubed on FC3 with all patches for some time.  I happen
> > > > > to install php5 (V5.1.0b2) recently and am just starting to use it.  So
> > > > > far I've been able to debug, but I cannot remove php V4.3.11 just yet. 
> > > > > 
> > > > > How did you install php5?  I was unable to find any rpms and had to
> > > > > build from source.
> > > > > 
> > > > > It looks to me as if their *might* be issues launching Gubed from
> > > > > StartSession.php with php5, but with my setup it is not clear yet if it
> > > > > is Gubed or my environment.  That is it seems to launch my php5 scripts
> > > > > as php4, attempting to force StartSession.php to run under php5 is
> > > > > problematic with my environment as it is.
> > > > > 
> > > > > Have your tried the Gubed debug client just to see if it will work? 
> > > > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > > > 
> > > > > Brett
> > > > > 
> > > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > > > <nmc...@bl...> said:
> > > > > > Hi Linus,
> > > > > > I hope the following info helps. All I really want to do is web/php with
> > > > > > debug. All this other hassle just drives me crazy :-)
> > > > > > 
> > > > > > Regards,
> > > > > > Nick
> > > > > > 
> > > > > > > Hello!
> > > > > > > 
> > > > > > > I'm not very familiar with Fedora, but I know there's been reports of strange 
> > > > > > > behaviour with Fedora and Quanta on the Quanta mailinglist.
> > > > > > > 
> > > > > > > It seems really strange that it works to telnet to 8016, but not to connect 
> > > > > > > with gubed. When you connect with telnet, do you get some text information?
> > > > > > > 
> > > > > > > Ill need a bit more of information:
> > > > > > > From what I understand you run both the webserver and quanta on the same box?
> > > > > > 
> > > > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > > > stuff configured here.
> > > > > > 
> > > > > > > 
> > > > > > > When you look at the index page of Gubed, there is a link to a 'debug info 
> > > > > > > page'. Could you look at that page and copy the debug information in your 
> > > > > > > next mail?
> > > > > > from the debug page:
> > > > > > Debug info 
> > > > > > If you wish to submit a support or bug request, please include the
> > > > > > output of this page in your request. It containts the most common
> > > > > > information the developers will need to help you. 
> > > > > > 
> > > > > >               Property
> > > > > >                Value
> > > > > > Gubed Version
> > > > > > 0.1.4
> > > > > > Protocol Version
> > > > > > 0.0.11
> > > > > > PHP Version
> > > > > > 5.0.4
> > > > > > Tokenizer
> > > > > > Yes
> > > > > > Backtrace
> > > > > > Yes
> > > > > > Server
> > > > > > Apache/2.0.54 (Fedora)
> > > > > > > 
> > > > > > > When you connect with telnet, do you get any text from quanta?
> > > > > > 
> > > > > > There is one line with "wait" then a couple of blank lines and thats
> > > > > > all. Exiting from Quanta then shows a "die" line.
> > > > > > 
> > > > > > > 
> > > > > > > I send this also to the gubed mailinglist, in case someone else has ideas
> > > > > > > 
> > > > > > > /Linus
> > > > > > > 
> > > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I'm completely new to linux and all I want to do is develop some web
> > > > > > > > stuff with php/mysql. But, I've been trying to get the debugger to work
> > > > > > > > with Quanta 3.4 and I keep getting "Unable to connect to debug server on
> > > > > > > > 127.0.0.1:8016."
> > > > > > > >
> > > > > > > > Now, I know the the debug server is listening by telnetting to port 8016
> > > > > > > > on localhost when quanta is running so I dont understand why debug
> > > > > > > > doesnt work for me. Its just driving me nuts!!!!
> > > > > > > >
> > > > > > > > I'm running "out of the box" Fedora RC4 and I followed the tutorial at
> > > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > > >
> > > > > > > > I'm getting really frustrated by how hard it is to get anything to work
> > > > > > > > with linux. Can you help?
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Nick
> > > > > > > 
> > > > > > 
> > > > > > 
> > > > > > 
> > > > > > -------------------------------------------------------
> > > > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > > > informative Webcasts and more! Get everything you need to get up to
> > > > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > > _______________________________________________
> > > > > > Gubed-devel mailing list
> > > > > > Gub...@li...
> > > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > > > -------------------------------------
> > > > > Brett C. Serkez, Technical Trainer
> > > > > 
> > > > > 
> > > > 
> > > -------------------------------------
> > > Brett C. Serkez, Technical Trainer
> > > 
> > > 
> > 
> -------------------------------------
> Brett C. Serkez, Technical Trainer
> 
> 

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Brett S. <tec...@se...>]

Nick,

The widgets are in Fedora extras.  This link describes how to setup for
extras and more:

http://fcp.homelinux.org/modules/smartfaq/faq.php?faqid=110

Then all you need to do is:

yum install wxGTK

Brett

On Sun, 03 Jul 2005 09:28:31 +0100, "Nick McCulloch"
<nmc...@bl...> said:
> Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> while Quanta just hung up completely! I had to logout-login to kill the
> quanta process.
> 
> So... I downloaded the Gubed 0.2.0 traball and tried to build the
> client. Seems it needs wxwindows which isn't part of RC3. Where do I
> find the rpm for that one?
> 
> linux just doesn't make life simple for newcomers to the OS !!!!
> 
> Nick
> On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > Nick,
> > 
> > I've been using Linux since almost the first Redhat release and closely
> > follow several distros.  Fedora is a very good distro for many reasons,
> > but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> > mailing list and while I think it will be a blow away release, FC3 with
> > all patches is a more stable environment.  The standard FC3 environment:
> > 
> > Gubed Version   0.2.0
> > Protocol Version        0.0.12
> > PHP Version     4.3.11
> > Tokenizer       Yes
> > Backtrace       Yes
> > Server  Apache/2.0.52 (Fedora)
> > 
> > I know Gubed works fine in this environment.  My issues revolved around
> > multiple users running out of their public_html directories, which you
> > can read about in existing posts on the mailing list, I was specific
> > about how to work around the issues.
> > 
> > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > kernel' from a command login before logging into the user interface the
> > first time.  The installation of the kernel requires a reboot. This
> > takes a while (I usually let it run over night), but once done, the
> > release is stable and reliable (and fast on old equipment).  I have a
> > couple of vintage mid-90 system running this environment, with multiple
> > users, everything is stable and fast.
> > 
> > I'll be experimenting with FC4 in a few weeks, once I see the number of
> > issues drop on their mailing list.  The biggest issue at this point is
> > the kernel is bloated, it needs triming, but I also think fair
> > adjustments are still being made to the overall environment.
> > 
> > Brett
> > 
> > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> > <nmc...@bl...> said:
> > > 
> > > Hi Brett,
> > > 
> > > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > > I'm afraid I'm not very "clued up" on linux as this is the first time
> > > I've stuck with a linux distro for more than a couple of weeks.
> > > 
> > > I may try the Gubed client shortly but I haven't had much success so far
> > > when it comes to installing from source/tarballs.
> > > 
> > > Maybe Linus can tell us if there are issues running with PHP5?
> > > 
> > > 
> > > > Nick,
> > > > 
> > > > I see you are running php V5.  It looks like you might be running Fedora
> > > > 3?
> > > > 
> > > > I've been using Gubed on FC3 with all patches for some time.  I happen
> > > > to install php5 (V5.1.0b2) recently and am just starting to use it.  So
> > > > far I've been able to debug, but I cannot remove php V4.3.11 just yet. 
> > > > 
> > > > How did you install php5?  I was unable to find any rpms and had to
> > > > build from source.
> > > > 
> > > > It looks to me as if their *might* be issues launching Gubed from
> > > > StartSession.php with php5, but with my setup it is not clear yet if it
> > > > is Gubed or my environment.  That is it seems to launch my php5 scripts
> > > > as php4, attempting to force StartSession.php to run under php5 is
> > > > problematic with my environment as it is.
> > > > 
> > > > Have your tried the Gubed debug client just to see if it will work? 
> > > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > > 
> > > > Brett
> > > > 
> > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > > <nmc...@bl...> said:
> > > > > Hi Linus,
> > > > > I hope the following info helps. All I really want to do is web/php with
> > > > > debug. All this other hassle just drives me crazy :-)
> > > > > 
> > > > > Regards,
> > > > > Nick
> > > > > 
> > > > > > Hello!
> > > > > > 
> > > > > > I'm not very familiar with Fedora, but I know there's been reports of strange 
> > > > > > behaviour with Fedora and Quanta on the Quanta mailinglist.
> > > > > > 
> > > > > > It seems really strange that it works to telnet to 8016, but not to connect 
> > > > > > with gubed. When you connect with telnet, do you get some text information?
> > > > > > 
> > > > > > Ill need a bit more of information:
> > > > > > From what I understand you run both the webserver and quanta on the same box?
> > > > > 
> > > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > > stuff configured here.
> > > > > 
> > > > > > 
> > > > > > When you look at the index page of Gubed, there is a link to a 'debug info 
> > > > > > page'. Could you look at that page and copy the debug information in your 
> > > > > > next mail?
> > > > > from the debug page:
> > > > > Debug info 
> > > > > If you wish to submit a support or bug request, please include the
> > > > > output of this page in your request. It containts the most common
> > > > > information the developers will need to help you. 
> > > > > 
> > > > >               Property
> > > > >                Value
> > > > > Gubed Version
> > > > > 0.1.4
> > > > > Protocol Version
> > > > > 0.0.11
> > > > > PHP Version
> > > > > 5.0.4
> > > > > Tokenizer
> > > > > Yes
> > > > > Backtrace
> > > > > Yes
> > > > > Server
> > > > > Apache/2.0.54 (Fedora)
> > > > > > 
> > > > > > When you connect with telnet, do you get any text from quanta?
> > > > > 
> > > > > There is one line with "wait" then a couple of blank lines and thats
> > > > > all. Exiting from Quanta then shows a "die" line.
> > > > > 
> > > > > > 
> > > > > > I send this also to the gubed mailinglist, in case someone else has ideas
> > > > > > 
> > > > > > /Linus
> > > > > > 
> > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm completely new to linux and all I want to do is develop some web
> > > > > > > stuff with php/mysql. But, I've been trying to get the debugger to work
> > > > > > > with Quanta 3.4 and I keep getting "Unable to connect to debug server on
> > > > > > > 127.0.0.1:8016."
> > > > > > >
> > > > > > > Now, I know the the debug server is listening by telnetting to port 8016
> > > > > > > on localhost when quanta is running so I dont understand why debug
> > > > > > > doesnt work for me. Its just driving me nuts!!!!
> > > > > > >
> > > > > > > I'm running "out of the box" Fedora RC4 and I followed the tutorial at
> > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > >
> > > > > > > I'm getting really frustrated by how hard it is to get anything to work
> > > > > > > with linux. Can you help?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nick
> > > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > -------------------------------------------------------
> > > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > > informative Webcasts and more! Get everything you need to get up to
> > > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > _______________________________________________
> > > > > Gubed-devel mailing list
> > > > > Gub...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > > -------------------------------------
> > > > Brett C. Serkez, Technical Trainer
> > > > 
> > > > 
> > > 
> > -------------------------------------
> > Brett C. Serkez, Technical Trainer
> > 
> > 
> 
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Linus M. <Li...@mc...>]

Hi

On the download page of wxwidgets, there are rpms, check http://wxwidgets.org/

And btw, if you had chosen for example Debian, all you would've needed to do 
is tell it to install wxwdigets and it would've done it for you ;)

But thats a discussion for a different mailinglist, I believe.. 

cheers

/Linus




On Sunday 03 July 2005 10.28, Nick McCulloch wrote:
> Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
> while Quanta just hung up completely! I had to logout-login to kill the
> quanta process.
>
> So... I downloaded the Gubed 0.2.0 traball and tried to build the
> client. Seems it needs wxwindows which isn't part of RC3. Where do I
> find the rpm for that one?
>
> linux just doesn't make life simple for newcomers to the OS !!!!
>
> Nick
>
> On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> > Nick,
> >
> > I've been using Linux since almost the first Redhat release and closely
> > follow several distros.  Fedora is a very good distro for many reasons,
> > but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> > mailing list and while I think it will be a blow away release, FC3 with
> > all patches is a more stable environment.  The standard FC3 environment:
> >
> > Gubed Version   0.2.0
> > Protocol Version        0.0.12
> > PHP Version     4.3.11
> > Tokenizer       Yes
> > Backtrace       Yes
> > Server  Apache/2.0.52 (Fedora)
> >
> > I know Gubed works fine in this environment.  My issues revolved around
> > multiple users running out of their public_html directories, which you
> > can read about in existing posts on the mailing list, I was specific
> > about how to work around the issues.
> >
> > If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> > kernel' from a command login before logging into the user interface the
> > first time.  The installation of the kernel requires a reboot. This
> > takes a while (I usually let it run over night), but once done, the
> > release is stable and reliable (and fast on old equipment).  I have a
> > couple of vintage mid-90 system running this environment, with multiple
> > users, everything is stable and fast.
> >
> > I'll be experimenting with FC4 in a few weeks, once I see the number of
> > issues drop on their mailing list.  The biggest issue at this point is
> > the kernel is bloated, it needs triming, but I also think fair
> > adjustments are still being made to the overall environment.
> >
> > Brett
> >
> > On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> >
> > <nmc...@bl...> said:
> > > Hi Brett,
> > >
> > > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > > I'm afraid I'm not very "clued up" on linux as this is the first time
> > > I've stuck with a linux distro for more than a couple of weeks.
> > >
> > > I may try the Gubed client shortly but I haven't had much success so
> > > far when it comes to installing from source/tarballs.
> > >
> > > Maybe Linus can tell us if there are issues running with PHP5?
> > >
> > > > Nick,
> > > >
> > > > I see you are running php V5.  It looks like you might be running
> > > > Fedora 3?
> > > >
> > > > I've been using Gubed on FC3 with all patches for some time.  I
> > > > happen to install php5 (V5.1.0b2) recently and am just starting to
> > > > use it.  So far I've been able to debug, but I cannot remove php
> > > > V4.3.11 just yet.
> > > >
> > > > How did you install php5?  I was unable to find any rpms and had to
> > > > build from source.
> > > >
> > > > It looks to me as if their *might* be issues launching Gubed from
> > > > StartSession.php with php5, but with my setup it is not clear yet if
> > > > it is Gubed or my environment.  That is it seems to launch my php5
> > > > scripts as php4, attempting to force StartSession.php to run under
> > > > php5 is problematic with my environment as it is.
> > > >
> > > > Have your tried the Gubed debug client just to see if it will work?
> > > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > >
> > > > Brett
> > > >
> > > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > >
> > > > <nmc...@bl...> said:
> > > > > Hi Linus,
> > > > > I hope the following info helps. All I really want to do is web/php
> > > > > with debug. All this other hassle just drives me crazy :-)
> > > > >
> > > > > Regards,
> > > > > Nick
> > > > >
> > > > > > Hello!
> > > > > >
> > > > > > I'm not very familiar with Fedora, but I know there's been
> > > > > > reports of strange behaviour with Fedora and Quanta on the Quanta
> > > > > > mailinglist.
> > > > > >
> > > > > > It seems really strange that it works to telnet to 8016, but not
> > > > > > to connect with gubed. When you connect with telnet, do you get
> > > > > > some text information?
> > > > > >
> > > > > > Ill need a bit more of information:
> > > > > > From what I understand you run both the webserver and quanta on
> > > > > > the same box?
> > > > >
> > > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > > stuff configured here.
> > > > >
> > > > > > When you look at the index page of Gubed, there is a link to a
> > > > > > 'debug info page'. Could you look at that page and copy the debug
> > > > > > information in your next mail?
> > > > >
> > > > > from the debug page:
> > > > > Debug info
> > > > > If you wish to submit a support or bug request, please include the
> > > > > output of this page in your request. It containts the most common
> > > > > information the developers will need to help you.
> > > > >
> > > > >               Property
> > > > >                Value
> > > > > Gubed Version
> > > > > 0.1.4
> > > > > Protocol Version
> > > > > 0.0.11
> > > > > PHP Version
> > > > > 5.0.4
> > > > > Tokenizer
> > > > > Yes
> > > > > Backtrace
> > > > > Yes
> > > > > Server
> > > > > Apache/2.0.54 (Fedora)
> > > > >
> > > > > > When you connect with telnet, do you get any text from quanta?
> > > > >
> > > > > There is one line with "wait" then a couple of blank lines and
> > > > > thats all. Exiting from Quanta then shows a "die" line.
> > > > >
> > > > > > I send this also to the gubed mailinglist, in case someone else
> > > > > > has ideas
> > > > > >
> > > > > > /Linus
> > > > > >
> > > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'm completely new to linux and all I want to do is develop
> > > > > > > some web stuff with php/mysql. But, I've been trying to get the
> > > > > > > debugger to work with Quanta 3.4 and I keep getting "Unable to
> > > > > > > connect to debug server on 127.0.0.1:8016."
> > > > > > >
> > > > > > > Now, I know the the debug server is listening by telnetting to
> > > > > > > port 8016 on localhost when quanta is running so I dont
> > > > > > > understand why debug doesnt work for me. Its just driving me
> > > > > > > nuts!!!!
> > > > > > >
> > > > > > > I'm running "out of the box" Fedora RC4 and I followed the
> > > > > > > tutorial at
> > > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > > >
> > > > > > > I'm getting really frustrated by how hard it is to get anything
> > > > > > > to work with linux. Can you help?
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nick
> > > > >
> > > > > -------------------------------------------------------
> > > > > SF.Net email is sponsored by: Discover Easy Linux Migration
> > > > > Strategies from IBM. Find simple to follow Roadmaps,
> > > > > straightforward articles, informative Webcasts and more! Get
> > > > > everything you need to get up to speed, fast.
> > > > > http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > > _______________________________________________
> > > > > Gubed-devel mailing list
> > > > > Gub...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > >
> > > > -------------------------------------
> > > > Brett C. Serkez, Technical Trainer
> >
> > -------------------------------------
> > Brett C. Serkez, Technical Trainer
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Nick M. <nmc...@bl...>]

Well, went back to RC3 and Quanta3.3 and Gubed "nearly" worked. After a
while Quanta just hung up completely! I had to logout-login to kill the
quanta process.

So... I downloaded the Gubed 0.2.0 traball and tried to build the
client. Seems it needs wxwindows which isn't part of RC3. Where do I
find the rpm for that one?

linux just doesn't make life simple for newcomers to the OS !!!!

Nick
On Thu, 2005-06-30 at 13:47 -0400, Brett Serkez wrote:
> Nick,
> 
> I've been using Linux since almost the first Redhat release and closely
> follow several distros.  Fedora is a very good distro for many reasons,
> but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> mailing list and while I think it will be a blow away release, FC3 with
> all patches is a more stable environment.  The standard FC3 environment:
> 
> Gubed Version   0.2.0
> Protocol Version        0.0.12
> PHP Version     4.3.11
> Tokenizer       Yes
> Backtrace       Yes
> Server  Apache/2.0.52 (Fedora)
> 
> I know Gubed works fine in this environment.  My issues revolved around
> multiple users running out of their public_html directories, which you
> can read about in existing posts on the mailing list, I was specific
> about how to work around the issues.
> 
> If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> kernel' from a command login before logging into the user interface the
> first time.  The installation of the kernel requires a reboot. This
> takes a while (I usually let it run over night), but once done, the
> release is stable and reliable (and fast on old equipment).  I have a
> couple of vintage mid-90 system running this environment, with multiple
> users, everything is stable and fast.
> 
> I'll be experimenting with FC4 in a few weeks, once I see the number of
> issues drop on their mailing list.  The biggest issue at this point is
> the kernel is bloated, it needs triming, but I also think fair
> adjustments are still being made to the overall environment.
> 
> Brett
> 
> On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> <nmc...@bl...> said:
> > 
> > Hi Brett,
> > 
> > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > I'm afraid I'm not very "clued up" on linux as this is the first time
> > I've stuck with a linux distro for more than a couple of weeks.
> > 
> > I may try the Gubed client shortly but I haven't had much success so far
> > when it comes to installing from source/tarballs.
> > 
> > Maybe Linus can tell us if there are issues running with PHP5?
> > 
> > 
> > > Nick,
> > > 
> > > I see you are running php V5.  It looks like you might be running Fedora
> > > 3?
> > > 
> > > I've been using Gubed on FC3 with all patches for some time.  I happen
> > > to install php5 (V5.1.0b2) recently and am just starting to use it.  So
> > > far I've been able to debug, but I cannot remove php V4.3.11 just yet. 
> > > 
> > > How did you install php5?  I was unable to find any rpms and had to
> > > build from source.
> > > 
> > > It looks to me as if their *might* be issues launching Gubed from
> > > StartSession.php with php5, but with my setup it is not clear yet if it
> > > is Gubed or my environment.  That is it seems to launch my php5 scripts
> > > as php4, attempting to force StartSession.php to run under php5 is
> > > problematic with my environment as it is.
> > > 
> > > Have your tried the Gubed debug client just to see if it will work? 
> > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > 
> > > Brett
> > > 
> > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > <nmc...@bl...> said:
> > > > Hi Linus,
> > > > I hope the following info helps. All I really want to do is web/php with
> > > > debug. All this other hassle just drives me crazy :-)
> > > > 
> > > > Regards,
> > > > Nick
> > > > 
> > > > > Hello!
> > > > > 
> > > > > I'm not very familiar with Fedora, but I know there's been reports of strange 
> > > > > behaviour with Fedora and Quanta on the Quanta mailinglist.
> > > > > 
> > > > > It seems really strange that it works to telnet to 8016, but not to connect 
> > > > > with gubed. When you connect with telnet, do you get some text information?
> > > > > 
> > > > > Ill need a bit more of information:
> > > > > From what I understand you run both the webserver and quanta on the same box?
> > > > 
> > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > stuff configured here.
> > > > 
> > > > > 
> > > > > When you look at the index page of Gubed, there is a link to a 'debug info 
> > > > > page'. Could you look at that page and copy the debug information in your 
> > > > > next mail?
> > > > from the debug page:
> > > > Debug info 
> > > > If you wish to submit a support or bug request, please include the
> > > > output of this page in your request. It containts the most common
> > > > information the developers will need to help you. 
> > > > 
> > > >               Property
> > > >                Value
> > > > Gubed Version
> > > > 0.1.4
> > > > Protocol Version
> > > > 0.0.11
> > > > PHP Version
> > > > 5.0.4
> > > > Tokenizer
> > > > Yes
> > > > Backtrace
> > > > Yes
> > > > Server
> > > > Apache/2.0.54 (Fedora)
> > > > > 
> > > > > When you connect with telnet, do you get any text from quanta?
> > > > 
> > > > There is one line with "wait" then a couple of blank lines and thats
> > > > all. Exiting from Quanta then shows a "die" line.
> > > > 
> > > > > 
> > > > > I send this also to the gubed mailinglist, in case someone else has ideas
> > > > > 
> > > > > /Linus
> > > > > 
> > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I'm completely new to linux and all I want to do is develop some web
> > > > > > stuff with php/mysql. But, I've been trying to get the debugger to work
> > > > > > with Quanta 3.4 and I keep getting "Unable to connect to debug server on
> > > > > > 127.0.0.1:8016."
> > > > > >
> > > > > > Now, I know the the debug server is listening by telnetting to port 8016
> > > > > > on localhost when quanta is running so I dont understand why debug
> > > > > > doesnt work for me. Its just driving me nuts!!!!
> > > > > >
> > > > > > I'm running "out of the box" Fedora RC4 and I followed the tutorial at
> > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > >
> > > > > > I'm getting really frustrated by how hard it is to get anything to work
> > > > > > with linux. Can you help?
> > > > > >
> > > > > > Regards,
> > > > > > Nick
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > informative Webcasts and more! Get everything you need to get up to
> > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > _______________________________________________
> > > > Gubed-devel mailing list
> > > > Gub...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > -------------------------------------
> > > Brett C. Serkez, Technical Trainer
> > > 
> > > 
> > 
> -------------------------------------
> Brett C. Serkez, Technical Trainer
> 
> 

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Brett S. <tec...@se...>]

My current environment has php4 as a module and php5 as a cli.

Brett

On Thu, 30 Jun 2005 20:54:35 +0200, "Linus McCabe" <Li...@mc...>
said:
> On Thursday 30 June 2005 19.28, Brett Serkez wrote:
> > It looks to me as if their *might* be issues launching Gubed from
> > StartSession.php with php5, but with my setup it is not clear yet if it
> > is Gubed or my environment.  That is it seems to launch my php5 scripts
> 
> I've been running php5 mostly from cli, Ill install it as an apache
> module and 
> give it a go to see if theres a different behaviour.
> 
> /L
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Gubed-devel mailing list
> Gub...@li...
> https://lists.sourceforge.net/lists/listinfo/gubed-devel
-------------------------------------
Brett C. Serkez, Technical Trainer

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Linus M. <Li...@mc...>]

On Thursday 30 June 2005 19.28, Brett Serkez wrote:
> It looks to me as if their *might* be issues launching Gubed from
> StartSession.php with php5, but with my setup it is not clear yet if it
> is Gubed or my environment.  That is it seems to launch my php5 scripts

I've been running php5 mostly from cli, Ill install it as an apache module and 
give it a go to see if theres a different behaviour.

/L

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Linus M. <Li...@mc...>]

Hi

Since I fixed all php5 problems a while ago, it's been working fine to me. 
Although, mostly i use php4.

/Linus

On Thursday 30 June 2005 19.37, Nick McCulloch wrote:
> Hi Brett,
>
> Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> I'm afraid I'm not very "clued up" on linux as this is the first time
> I've stuck with a linux distro for more than a couple of weeks.
>
> I may try the Gubed client shortly but I haven't had much success so far
> when it comes to installing from source/tarballs.
>
> Maybe Linus can tell us if there are issues running with PHP5?
>
> > Nick,

Re: [gbd-dev] Re: QUANTA/Gubed - getting it to work?

[Nick M. <nmc...@bl...>]

Brett,
I notice from the debug details the you are using Gubd 0.2.0. The
Gubed_Quanta package indicates version 0.1.4. Do you think that would
have anything to do with my problem?

Nick
> Nick,
> 
> I've been using Linux since almost the first Redhat release and closely
> follow several distros.  Fedora is a very good distro for many reasons,
> but I'm not sure FC4 is the best place to start.  I'm on the Fedora
> mailing list and while I think it will be a blow away release, FC3 with
> all patches is a more stable environment.  The standard FC3 environment:
> 
> Gubed Version   0.2.0
> Protocol Version        0.0.12
> PHP Version     4.3.11
> Tokenizer       Yes
> Backtrace       Yes
> Server  Apache/2.0.52 (Fedora)
> 
> I know Gubed works fine in this environment.  My issues revolved around
> multiple users running out of their public_html directories, which you
> can read about in existing posts on the mailing list, I was specific
> about how to work around the issues.
> 
> If you install FC3, make sure to run 'up2date -u' and 'up2date -if
> kernel' from a command login before logging into the user interface the
> first time.  The installation of the kernel requires a reboot. This
> takes a while (I usually let it run over night), but once done, the
> release is stable and reliable (and fast on old equipment).  I have a
> couple of vintage mid-90 system running this environment, with multiple
> users, everything is stable and fast.
> 
> I'll be experimenting with FC4 in a few weeks, once I see the number of
> issues drop on their mailing list.  The biggest issue at this point is
> the kernel is bloated, it needs triming, but I also think fair
> adjustments are still being made to the overall environment.
> 
> Brett
> 
> On Thu, 30 Jun 2005 18:37:51 +0100, "Nick McCulloch"
> <nmc...@bl...> said:
> > 
> > Hi Brett,
> > 
> > Thanks for the reply. I'm running Fedora RC4 which has PHP5 included.
> > I'm afraid I'm not very "clued up" on linux as this is the first time
> > I've stuck with a linux distro for more than a couple of weeks.
> > 
> > I may try the Gubed client shortly but I haven't had much success so far
> > when it comes to installing from source/tarballs.
> > 
> > Maybe Linus can tell us if there are issues running with PHP5?
> > 
> > 
> > > Nick,
> > > 
> > > I see you are running php V5.  It looks like you might be running Fedora
> > > 3?
> > > 
> > > I've been using Gubed on FC3 with all patches for some time.  I happen
> > > to install php5 (V5.1.0b2) recently and am just starting to use it.  So
> > > far I've been able to debug, but I cannot remove php V4.3.11 just yet. 
> > > 
> > > How did you install php5?  I was unable to find any rpms and had to
> > > build from source.
> > > 
> > > It looks to me as if their *might* be issues launching Gubed from
> > > StartSession.php with php5, but with my setup it is not clear yet if it
> > > is Gubed or my environment.  That is it seems to launch my php5 scripts
> > > as php4, attempting to force StartSession.php to run under php5 is
> > > problematic with my environment as it is.
> > > 
> > > Have your tried the Gubed debug client just to see if it will work? 
> > > Have you tried regressing to php4 to see if it will work with Quanta?
> > > 
> > > Brett
> > > 
> > > On Thu, 30 Jun 2005 17:19:15 +0100, "Nick McCulloch"
> > > <nmc...@bl...> said:
> > > > Hi Linus,
> > > > I hope the following info helps. All I really want to do is web/php with
> > > > debug. All this other hassle just drives me crazy :-)
> > > > 
> > > > Regards,
> > > > Nick
> > > > 
> > > > > Hello!
> > > > > 
> > > > > I'm not very familiar with Fedora, but I know there's been reports of strange 
> > > > > behaviour with Fedora and Quanta on the Quanta mailinglist.
> > > > > 
> > > > > It seems really strange that it works to telnet to 8016, but not to connect 
> > > > > with gubed. When you connect with telnet, do you get some text information?
> > > > > 
> > > > > Ill need a bit more of information:
> > > > > From what I understand you run both the webserver and quanta on the same box?
> > > > 
> > > > Thats correct. apache is a "straight from the cd" setup. No special
> > > > stuff configured here.
> > > > 
> > > > > 
> > > > > When you look at the index page of Gubed, there is a link to a 'debug info 
> > > > > page'. Could you look at that page and copy the debug information in your 
> > > > > next mail?
> > > > from the debug page:
> > > > Debug info 
> > > > If you wish to submit a support or bug request, please include the
> > > > output of this page in your request. It containts the most common
> > > > information the developers will need to help you. 
> > > > 
> > > >               Property
> > > >                Value
> > > > Gubed Version
> > > > 0.1.4
> > > > Protocol Version
> > > > 0.0.11
> > > > PHP Version
> > > > 5.0.4
> > > > Tokenizer
> > > > Yes
> > > > Backtrace
> > > > Yes
> > > > Server
> > > > Apache/2.0.54 (Fedora)
> > > > > 
> > > > > When you connect with telnet, do you get any text from quanta?
> > > > 
> > > > There is one line with "wait" then a couple of blank lines and thats
> > > > all. Exiting from Quanta then shows a "die" line.
> > > > 
> > > > > 
> > > > > I send this also to the gubed mailinglist, in case someone else has ideas
> > > > > 
> > > > > /Linus
> > > > > 
> > > > > On Wednesday 29 June 2005 16.50, you wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I'm completely new to linux and all I want to do is develop some web
> > > > > > stuff with php/mysql. But, I've been trying to get the debugger to work
> > > > > > with Quanta 3.4 and I keep getting "Unable to connect to debug server on
> > > > > > 127.0.0.1:8016."
> > > > > >
> > > > > > Now, I know the the debug server is listening by telnetting to port 8016
> > > > > > on localhost when quanta is running so I dont understand why debug
> > > > > > doesnt work for me. Its just driving me nuts!!!!
> > > > > >
> > > > > > I'm running "out of the box" Fedora RC4 and I followed the tutorial at
> > > > > > http://www.very-clever.com/quanta-gubed-debugging.php
> > > > > >
> > > > > > I'm getting really frustrated by how hard it is to get anything to work
> > > > > > with linux. Can you help?
> > > > > >
> > > > > > Regards,
> > > > > > Nick
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > -------------------------------------------------------
> > > > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > > > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > > > informative Webcasts and more! Get everything you need to get up to
> > > > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > > > _______________________________________________
> > > > Gubed-devel mailing list
> > > > Gub...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/gubed-devel
> > > -------------------------------------
> > > Brett C. Serkez, Technical Trainer
> > > 
> > > 
> > 
> -------------------------------------
> Brett C. Serkez, Technical Trainer
> 
>