lxr-developer — Don't use, active developers only

[Lxr-dev] [ lxr-Bugs-726798 ] ctags options are wrong

[SourceForge.net <no...@so...>]

Bugs item #726798, was opened at 2003-04-24 11:13
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=726798&group_id=27350

Category: genxref
Group: current cvs
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Malcolm Box (mbox)
Assigned to: Malcolm Box (mbox)
Summary: ctags options are wrong

Initial Comment:
Genxref currently hard codes the --lang-options to
ectags.  This results in confusing output that the rest
of Generic.pm is not able to handle.

The fix is to make the parameters to ectags language
dependent - ie extend the generic.conf structures.

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2004-07-12 15:44

Message:
Logged In: YES 
user_id=215386

Fixed I think - we now force the language appropriately, and
the options are all language specific.  Result is that
ectags ignores the ones that don't apply to the specific
language.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=726798&group_id=27350

[Lxr-dev] [ lxr-Bugs-837424 ] Tweaks for cleaner out-of-box setup

[SourceForge.net <no...@so...>]

Bugs item #837424, was opened at 2003-11-06 18:48
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=837424&group_id=27350

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Tweaks for cleaner out-of-box setup

Initial Comment:
I finally got LXR running on my system, after getting
all the
prerequisite software installed (apache, a recent perl,
mod_perl,
the right compilers so I could build a mod_perl which
matches
my binary apache and perl installations, mysql, DBI,
DBD, ctags.)
LXR itself actually wasn't too hard to get going (using
files, not CVS),
although I did have to tweak a couple things relative
to the lxr-0.9.2 
distribution:

Fix syntax in initdb-mysql (from current CVS).

Remove redundant code from html-ident.html:

--- html-ident.html.orig        2003-09-25
16:23:19.250145370 -0500
+++ html-ident.html     2003-10-23 14:08:06.178594590 -0500
@@ -21,11 +21,3 @@
   <td>$fileref</td><td>$type</td><td>$rel</td>
 </tr>}
 </table>
-
-<p>
-<table>
-<tr><td colspan='2'><b>References:</b></td></tr>
-$uses{<tr>
-  <td width='30'>   </td><td>$fileref</td>
-</tr>}
-</table>


Print a clean error message in the search script, since
I don't have
freetext searching enabled:

--- search.orig 2003-09-25 16:23:19.078751407 -0500
+++ search      2003-10-23 14:13:15.238335665 -0500
@@ -166,6 +166,9 @@
        elsif ($config->swishsearch and
$config->swishdir) {
            swishsearch($searchtext);
        }
+       else {
+           warning("No freetext search engine
configured.");
+       }
     }
 }


Now I just need to tie LXR in to my company's internal
source-
control system....

Thanks for a great indexing system!

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2004-07-12 13:52

Message:
Logged In: YES 
user_id=215386

Thanks for the tidy-ups.  These have now been incorporated
in CVS.

Good luck with integrating with the SCM system - which one
are you looking at?  We're always interested in extensions
for alternative SCM systems.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=837424&group_id=27350

[Lxr-dev] [ lxr-Bugs-966613 ] Identifier search provides random answers

[SourceForge.net <no...@so...>]

Bugs item #966613, was opened at 2004-06-04 16:33
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=966613&group_id=27350

Category: genxref
Group: v0.3
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Identifier search provides random answers

Initial Comment:
   I am using LXR for indexing large software project
(15000 files). LXR 0.3 worked OK on Linux RH 7.3,
perl 5.6.0. After the machine was upgraded to
Linux CEL3 with perl 5.8.0 the identifier seach
does provide correct answers for some identifiers
and wrong answers for others (wrong answer means
that all provided references are incorrect).
Any idea why change of OS/perl version can make a 
difference for LXR? 

        Thanks in advance,

              Alex Undrus <un...@bn...>   

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2004-07-12 13:40

Message:
Logged In: YES 
user_id=215386

This bug is unlikely to be fixed in 0.3 as it is no longer being
actively worked on.

Please try to reproduce using the latest development release.  If
you can reproduce it then please update the bug to record this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=966613&group_id=27350

[Lxr-dev] [ lxr-Bugs-640589 ] File search with swish-e

[SourceForge.net <no...@so...>]

Bugs item #640589, was opened at 2002-11-19 09:40
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640589&group_id=27350

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Johan Vermeire (jvme_be)
Assigned to: Nobody/Anonymous (nobody)
Summary: File search with swish-e

Initial Comment:
Hi,

I've set-up the LXR tool (version 0.9.2) with swish-e
on a Solaris 2.8 system.
After a few  patches everthing seems to work with
the swish-e interface, except the "file search".

In the search perl script, there is only a method with 
glimpse by using the file:
$config->glimpsedir."/.glimpse_filenames".

The search perl script doesn't has a method for swish-e.
Has anybody already completed this?
I'm willing to do this, but I don't know yet how difficult
this is .
Which script are impacted?
- find 
- genxref
...

Another solution is to use glimpse as search engine.
But I've the impression that swish-e is more powerfull.

Regards,
Johan

----------------------------------------------------------------------

>Comment By: Malcolm Box (mbox)
Date: 2004-07-12 13:38

Message:
Logged In: YES 
user_id=215386

Fixed in CVS

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640589&group_id=27350

[Lxr-dev] Re: [Lxr-commits] CVS: lxr find,1.13,1.14

[Malcolm B. <ma...@br...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave Brondsema wrote:

| Update of /cvsroot/lxr/lxr
| In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22905
|
| Modified Files:
| 	find
| Log Message:
| option for basic and regexp search; option for case-sensitivity
|

Quick suggestion on this - if you're going to be adding lots of new cool
features to the find & search commands that will be swish-e specific,
then it may be a good time to move away from hardcoded HTML in the perl
and over to a template such as for ident.  That way we can supply two
different templates, one for glimpse (without all the options that it
can't support) and one for swish-e.

Plus it will be a nice move away from the remaining hard-coded HTML.

Cheers,

Malcolm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org

iD8DBQFA7QcvQeMefPKyX/QRArhZAKCteaxYLMd5kp7xm9/h5cHyexjITwCeMLel
QUFdssijcYnGl9J251smo8Y=
=4ePU
-----END PGP SIGNATURE-----

[Lxr-dev] [ lxr-Bugs-489866 ] --allversions doesn't work

[SourceForge.net <no...@so...>]

Bugs item #489866, was opened at 2001-12-06 09:47
Message generated for change (Comment added) made by brondsem
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=489866&group_id=27350

Category: genxref
Group: current cvs
Status: Open
Resolution: None
Priority: 8
Submitted By: Malcolm Box (mbox)
Assigned to: Peder O. Klingenberg (pok)
Summary: --allversions doesn't work

Initial Comment:
This is a tracking bug for the the CVS.pm changes
needed to make --allversions work properly across CVS
and Files.

Currently one or the other works - we need both to work
with the same semantics before 1.00

----------------------------------------------------------------------

>Comment By: Dave Brondsema (brondsem)
Date: 2004-07-07 15:45

Message:
Logged In: YES 
user_id=341298

The versions for CVS.pm are branches and tags.  These can be
applied at any level of the codebase, so for example version
'branch-for-feature-X' might only exist in
myapp/src/component/foo and nowhere else in the codebase. 
It wouldn't make sense for --allversions to index this
version.  The best solution I can think of is for
--allversions to index the default version.  I already
modified genxref to display an error if --allversions is
used but the version range returns nothing (as is the case
with CVS).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=489866&group_id=27350

Re: [Lxr-dev] support only swish-e?

[Dave B. <da...@br...>]

On Wed, 7 Jul 2004, Malcolm Box wrote:

> Dave Brondsema wrote:
>
> | Would it be ok to support only swish-e and not glimpse?  This would
> | make LXR code easier to maintain and would allow us to take
> | advantage of some features (like searching on content and filepath
> | together).
> |
> | swish-e runs on all platforms that glimpse does, and has no
> | restrictions on its use, so I don't think this would be a problem
> | for LXR users to install.
>
> My take is that this will be fine, so long as swish-e is really ready
> for production use.  Last time I looked it was definitely in a beta
> state, and I ran into problems with it on large codebases (600MB
> plus).  So I'd like to see some evidence that it can handle that sort
> of load before we remove glimpse support.
>
> If you wanted to add the additional features conditionally on swish-e
> presence then that would be totally fine.
>
> Cheers,
>
> Malcolm

The codebase at our company is 700+MB and almost 4 million lines of code.
swish-e is runs fine on it.

I'll add the swish-e features and keep glimpse support too.

-- 
Dave Brondsema : da...@br...
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org

[Lxr-dev] CVS support

[Malcolm B. <ma...@br...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dave,

I notice you've been adding some new stuff round CVS, so I'm guessing
you're using it.

Would you be willing/able to take a look at the long-standing defects
with CVS - I'm thinking of:

[ 526664 ] CVS {default}=head != co default
http://sourceforge.net/tracker/index.php?func=detail&aid=526664&group_id=27350&atid=390117

and

[ 489866 ] --allversions doesn't work
http://sourceforge.net/tracker/index.php?func=detail&aid=489866&group_id=27350&atid=390117

Especially the latter one.  From what I recall, the issue was around how
to construct the versions set - Files.pm has a fixed set that is known
in advance, whereas the set of CVS versions (tags) can only be found by
looking at every file individually.  There's the added question about
what to do about CVS versions that aren't tagged - right now I think
they don't get indexed at all.

Would be great if you could find some time to look at these and fix them
- - they're two of the 1.0 blockers IMHO.

Cheers,

Malcolm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org

iD8DBQFA7BdjQeMefPKyX/QRArT6AJ9/aGlNZ8rJWNfMhe2uTfXE22NLMwCeOUKA
e8rd8QYoeq3Y/KKYQT0zRuU=
=fNK0
-----END PGP SIGNATURE-----

Re: [Lxr-dev] support only swish-e?

[Malcolm B. <ma...@br...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Dave Brondsema wrote:

| Would it be ok to support only swish-e and not glimpse?  This would
| make LXR code easier to maintain and would allow us to take
| advantage of some features (like searching on content and filepath
| together).
|
| swish-e runs on all platforms that glimpse does, and has no
| restrictions on its use, so I don't think this would be a problem
| for LXR users to install.

My take is that this will be fine, so long as swish-e is really ready
for production use.  Last time I looked it was definitely in a beta
state, and I ran into problems with it on large codebases (600MB
plus).  So I'd like to see some evidence that it can handle that sort
of load before we remove glimpse support.

If you wanted to add the additional features conditionally on swish-e
presence then that would be totally fine.

Cheers,

Malcolm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org
 
iD8DBQFA7BTLQeMefPKyX/QRAq+DAKDDC9Ab7XtwUJLWUm9maXT+nQwPaQCg1ppA
fa32IevQ70ffm3xYEAeaSjs=
=DcgV
-----END PGP SIGNATURE-----

[Lxr-dev] support only swish-e?

[Dave B. <da...@br...>]

Would it be ok to support only swish-e and not glimpse?  This would make
LXR code easier to maintain and would allow us to take advantage of some
features (like searching on content and filepath together).

swish-e runs on all platforms that glimpse does, and has no restrictions
on its use, so I don't think this would be a problem for LXR users to
install.

-- 
Dave Brondsema : da...@br...
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org

Re: [Lxr-dev] Welcome to a new developer

[Jan-Benedict G. <jb...@lu...>]

On Mon, 2004-07-05 08:28:05 -0400, Dave Brondsema <da...@br...>
wrote in message <40E...@br...>:
> Jan-Benedict Glaw wrote:
> >On Mon, 2004-07-05 09:51:27 +0100, Malcolm Box=20
> ><ma...@br...>
> >wrote in message <40E...@br...>:
> >
> >So "Thanks for the good work, Dave!" as in No News Are Good News.
>=20
> Thanks!  It's nice to hear some feedback; it was a little weird making=20
> so many changes as a newcomer without hearing any response.

Well, that's the downside of free software: since you normally don't
earn money for the code, nor hear any comments (except criticism if you
broke something), you get little to no feedback most of the time.

So a hint for all hackers: try to find our which sites actually do use
your software. Place some nice version string or the like into the code
and see if you can find them with google:) However, if you work on code
that's little used (eg. LXR. I'm working for example on porting Linux to
the VAX, ...) you'll find a hard time to find any traces. In that case,
just be happy that it works for you!

MfG, JBG

--=20
   Jan-Benedict Glaw       jb...@lu...    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier B=FCrger" | im Internet! |   im Ira=
k!
   ret =3D do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TC=
PA));

Re: [Lxr-dev] Welcome to a new developer

[Dave B. <da...@br...>]

Jan-Benedict Glaw wrote:
> On Mon, 2004-07-05 09:51:27 +0100, Malcolm Box <ma...@br...>
> wrote in message <40E...@br...>:
> 
> 
>>Once again, welcome to Dave and I look forward to more activity on 
>>lxr-dev & CVS in the future.
> 
> 
> I've seen the last checkins but didn't speak up so far. I strongly
> second your welcome: the patches are quite nice, make LXR more stable
> in some corner cases, add some new functionality, ...
> 
> So "Thanks for the good work, Dave!" as in No News Are Good News.
> 
> MfG, JBG
> 

Thanks!  It's nice to hear some feedback; it was a little weird making 
so many changes as a newcomer without hearing any response.

-- 
Dave Brondsema : da...@br...
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal

Re: [Lxr-dev] Welcome to a new developer

[Jan-Benedict G. <jb...@lu...>]

On Mon, 2004-07-05 09:51:27 +0100, Malcolm Box <ma...@br....u=
k>
wrote in message <40E...@br...>:

> Once again, welcome to Dave and I look forward to more activity on=20
> lxr-dev & CVS in the future.

I've seen the last checkins but didn't speak up so far. I strongly
second your welcome: the patches are quite nice, make LXR more stable
in some corner cases, add some new functionality, ...

So "Thanks for the good work, Dave!" as in No News Are Good News.

MfG, JBG

--=20
   Jan-Benedict Glaw       jb...@lu...    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier B=FCrger" | im Internet! |   im Ira=
k!
   ret =3D do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TC=
PA));

[Lxr-dev] Welcome to a new developer

[Malcolm B. <ma...@br...>]

Hi,

As some of you may have noticed, there's been a flurry of CVS commits 
recently from Dave Brondsema.  I'd like to welcome him to the LXR 
development team - it's great to have more developers aboard.

If anyone else wants to join the development team, the process is pretty 
simple:

1. post some patches either to lxr-developer or sourceforge
2. send me a mail asking to join, and giving some indication of  what 
you want to be working on.

If the patches look good, and the bit you want to work on needs help 
(and that's pretty much everywhere!), then I'll add you to the 
developers group.  But the patches come first!

Once again, welcome to Dave and I look forward to more activity on 
lxr-dev & CVS in the future.

Cheers,

Malcolm

Re: [Lxr-dev] [ lxr-Bugs-640593 ] File search with swish-e

[Malcolm B. <ma...@br...>]

SourceForge.net wrote:

>Bugs item #640593, was opened at 2002-11-19 04:51
>  
>
<snip>

>Comment By: Dave Brondsema (brondsem)
>
>this is fixed in CVS.. I don't have rights to close the bug
>though
>  
>
You should have rights to close bugs & patches now.  I've closed this 
one anyway though.

Cheers,

Malcolm

[Lxr-dev] [ lxr-Bugs-640593 ] File search with swish-e

[SourceForge.net <no...@so...>]

Bugs item #640593, was opened at 2002-11-19 09:51
Message generated for change (Settings changed) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640593&group_id=27350

Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Johan Vermeire (jvme_be)
>Assigned to: Dave Brondsema (brondsem)
Summary: File search with swish-e

Initial Comment:
Hi,

I've set-up the LXR tool (version 0.9.2) with swish-e
on a Solaris 2.8 system.
After a few  patches everthing seems to work with
the swish-e interface, except the "file search".

In the search perl script, there is only a method with 
glimpse by using the file:
$config->glimpsedir."/.glimpse_filenames".

The search perl script doesn't has a method for swish-e.
Has anybody already completed this?
I'm willing to do this, but I don't know yet how difficult
this is .
Which script are impacted?
- find 
- genxref
...

Another solution is to use glimpse as search engine.
But I've the impression that swish-e is more powerfull.

Regards,
Johan

----------------------------------------------------------------------

Comment By: Dave Brondsema (brondsem)
Date: 2004-06-30 14:54

Message:
Logged In: YES 
user_id=341298

this is fixed in CVS.. I don't have rights to close the bug
though

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640593&group_id=27350

[Lxr-dev] [ lxr-Bugs-640593 ] File search with swish-e

[SourceForge.net <no...@so...>]

Bugs item #640593, was opened at 2002-11-19 04:51
Message generated for change (Comment added) made by brondsem
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640593&group_id=27350

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Johan Vermeire (jvme_be)
Assigned to: Nobody/Anonymous (nobody)
Summary: File search with swish-e

Initial Comment:
Hi,

I've set-up the LXR tool (version 0.9.2) with swish-e
on a Solaris 2.8 system.
After a few  patches everthing seems to work with
the swish-e interface, except the "file search".

In the search perl script, there is only a method with 
glimpse by using the file:
$config->glimpsedir."/.glimpse_filenames".

The search perl script doesn't has a method for swish-e.
Has anybody already completed this?
I'm willing to do this, but I don't know yet how difficult
this is .
Which script are impacted?
- find 
- genxref
...

Another solution is to use glimpse as search engine.
But I've the impression that swish-e is more powerfull.

Regards,
Johan

----------------------------------------------------------------------

Comment By: Dave Brondsema (brondsem)
Date: 2004-06-30 09:54

Message:
Logged In: YES 
user_id=341298

this is fixed in CVS.. I don't have rights to close the bug
though

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=640593&group_id=27350

[Lxr-dev] fixes and improvements

[Dave B. <da...@br...>]

I've installed LXR from CVS and have it up and running.  However there are
many fixes and improvements that I'd like to contribute.  For example:

filename searching for swish-e
add icons to repository
ignore binaries in freetext search
ignore CVS files in 'Attic' when appropriate
# of matches on search results

I've attached a patch that implements filename searching for swish-e.  If
you're willing to add me as a developer so I can commit directly, my SF
account is 'brondsem'.

Thanks!

-- 
Dave Brondsema : da...@br...
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org

Re: [Lxr-dev] another problems

[Malcolm B. <ma...@br...>]

George Ciobanu wrote:

> /** Fatal: Ident refs template not configured at /usr/local/lxr/ident 
> line 125./
>
> Does anybody know how to fix this ?
>
Yes, you need to make sure that your lxr.conf has a entry such as:

 'htmlident_refs'  => 'html-ident-refs.html',

and that the filename referenced exists in the lxr directory (the same 
directory as the lxr.conf file).

> Browsing a directory called "g++fec" gives this message
>
> /** Fatal: Can't open /src/orc-2.1/osprey1.0/g fe/ at 
> /usr/local/lib/site_perl/LXR/Files/Plain.pm line 104. / 

The httpwash function in Common.pm is being a bit overzealous.  Comment 
out the line "    $t =~ s/\+/ /g;" to fix this - but be aware that this 
could result in a security hole being opened (I have not verified that 
there is no attack potential in the "+" character.)

> Also, can u tell me where I can get the pictures for the folders and 
> files and where to put them.
>
The pictures for files/folders I use are from the Apache distribution.  
The URL used to load them is http://yourhost/icons/folder.gif, so put 
the icon files wherever this refers to on your server (usually Apache 
has an alias for /icons/ to some directory).  Alternatively you can 
change the paths in the "source" program to point to wherever you like.

> P.S. Malcolm, I'm sorry for sending this to you twice.
>
No problem.

Cheers,

Malcolm

[Lxr-dev] another problems

[George C. <cda...@ya...>]

Thanks for all the info. I still have some problems though. Browsing seems to be ok. But when I try to look for a variable i get this :
 
** Fatal: Ident refs template not configured at /usr/local/lxr/ident line 125.

Does anybody know how to fix this ? 

Browsing a directory called "g++fec" gives this message 
** Fatal: Can't open /src/orc-2.1/osprey1.0/g fe/ at /usr/local/lib/site_perl/LXR/Files/Plain.pm line 104. 
Also, can u tell me where I can get the pictures for the folders and files and where to put them. 

P.S. Malcolm, I'm sorry for sending this to you twice.

Thanks and regards, 
George


		
---------------------------------
Do you Yahoo!?
Friends.  Fun. Try the all-new Yahoo! Messenger

[Lxr-dev] [ lxr-Bugs-966613 ] Identifier search provides random answers

[SourceForge.net <no...@so...>]

Bugs item #966613, was opened at 2004-06-04 08:33
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=966613&group_id=27350

Category: genxref
Group: v0.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Identifier search provides random answers

Initial Comment:
   I am using LXR for indexing large software project
(15000 files). LXR 0.3 worked OK on Linux RH 7.3,
perl 5.6.0. After the machine was upgraded to
Linux CEL3 with perl 5.8.0 the identifier seach
does provide correct answers for some identifiers
and wrong answers for others (wrong answer means
that all provided references are incorrect).
Any idea why change of OS/perl version can make a 
difference for LXR? 

        Thanks in advance,

              Alex Undrus <un...@bn...>   

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=966613&group_id=27350

Re: [Lxr-dev] source question

[George C. <cda...@ya...>]

Hello,
 
Thanks for the prompt response. I'm using Apache 1.3.29,  perl 5.8.3. When I try to issue a continue command. I get this error :
 
syntax error at (eval 8)[/usr/share/perl/5.8/perl5db.pl:619] line 2, near ";
continue"

Here's what I found there. I'm a perl newbie, so I don't know what this is. Any ideas ?
 
        # $usercontext built in DB::DB near the comment                         
        # "set up the context for DB::eval ..."                                 
        # Evaluate and save any results.                                        
        @res =                                                                  
  619:        eval "$usercontext $evalarg;\n";    # '\n' for nice recursive debug   
                                                                                
        # Restore those old values.                                             
        $trace  = $otrace;                                                      
        $single = $osingle;                                                     
        $^D     = $od;                                                          
    }                                                                           

Thanks and regards,
George
                                                                                
  Malcolm Box <ma...@br...> wrote:
George Ciobanu wrote:

> So source output is definetely not ok. Is there a way to test the 
> source script, to see the generated output.
>
I take back my earlier comment that there wasn't a good way. What you 
can do is:

- run source under the perl debugger:
"perl -d ./source"

- then set up the environment that the script depends on:
$ENV{'SERVER_NAME'}="your server name";
$ENV{'SERVER_PORT'}=80;
$ENV{'SCRIPT_NAME'}="/lxr";

the values you should set for these variables should match the baseurl 
in your lxr.conf so that "http://$ENV{'SERVER_NAME'}$ENV{'SCRIPT_NAME'}" 
matches the URL.

- Run the script - "continue"

You will then get the script output dumped to the console.

Hope this lets you debug the problem.

Cheers,

Malcolm
		
---------------------------------
Do you Yahoo!?
Friends.  Fun. Try the all-new Yahoo! Messenger

Re: [Lxr-dev] source question

[Malcolm B. <ma...@br...>]

George Ciobanu wrote:

> So source output is definetely not ok. Is there a way to test the 
> source script, to see the generated output.
>
I take back my earlier comment that there wasn't a good way.  What you 
can do is:

- run source under the perl debugger:
"perl -d ./source"

- then set up the environment that the script depends on:
$ENV{'SERVER_NAME'}="your server name";
$ENV{'SERVER_PORT'}=80;
$ENV{'SCRIPT_NAME'}="/lxr";

the values you should set for these variables should match the baseurl 
in your lxr.conf so that "http://$ENV{'SERVER_NAME'}$ENV{'SCRIPT_NAME'}" 
matches the URL.

- Run the script - "continue"

You will then get the script output dumped to the console.

Hope this lets you debug the problem.

Cheers,

Malcolm

Re: [Lxr-dev] source question

[Malcolm B. <ma...@br...>]

Hi George,

George Ciobanu wrote:

> I'm sorry for all the previous incomplete or misleading information 
> before. The fact is I really need to get the lxr engine working. In 
> the error log for apache I get a
>
> malformed header from script. Bad header=HTTP/1.0 200 OK: 
> /usr/local/lxr/source
>
> So source output is definetely not ok. Is there a way to test the 
> source script, to see the generated output.
>
There's no easy way to run the source script to see the output that I 
know of, as it , as it is a mod_perl script that needs the Apache 
environment.  Anyone else got a suggestion?

Are you sure that your Apache setup is picking up & obeying the 
.htaccess file from the lxr distribution?  That should set things up so 
that the header is OK - the normal problem reported is people seeing an 
extra header, not a Bad Header error.

Also, what version of Apache are you using?  Apache used to parse 
headers from CGI scripts, it should no longer be doing so if you're 
using a modern version.

I suggest doing some googling for "bad header" and "nph cgi" to find out 
more about how Apache is handling script output.

I've also had a look at your lxr.conf, and there's a couple of potential 
problems:

- the 'sourceroot' variable should be set to an absolute path, it's not 
relative to any of the other paths
- you probably don't need the 'strip' variable to be set

Hope this helps you on your way. 

Cheers,

Malcolm

[Lxr-dev] source question

[George C. <cda...@ya...>]

Hello,

I'm sorry for all the previous incomplete or misleading information before. The fact is I really need to get the lxr engine working. In the error log for apache I get a 

malformed header from script. Bad header=HTTP/1.0 200 OK: /usr/local/lxr/source

So source output is definetely not ok. Is there a way to test the source script, to see the generated output.

Thank you,

George



		
---------------------------------
Do you Yahoo!?
Friends.  Fun. Try the all-new Yahoo! Messenger