Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <41B473F2.5040300@apache.org>
Date: Mon, 06 Dec 2004 10:00:02 -0500
From: Enrique Rodriguez <erodriguez@apache.org>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041103)
MIME-Version: 1.0
To: Apache Directory Developers List <directory-dev@incubator.apache.org>
Subject: Re: [eve] GQ exhibits unusual behavoir
References: <41B3ECB3.90905@bellsouth.net>
In-Reply-To: <41B3ECB3.90905@bellsouth.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alex Karasulu wrote:
> Enrique,
> 
> Since you work with GQ can you look into a way I can debug this app to 
> see why it cannot show me entry attributes?  I can't find a way to get 
> any information from it.

You can get good output from GQ with 'strace':

$ strace gq

The '-o temp.txt' for output to a file might come in handy, since it 
will pump out tons of text, so much so that it may slow the app down 
enough to make double-clicking hard.

I found one problem this way, that is if you set GQ to prompt for a 
password on first connect, it doesn't appear to actually use the 
password you enter.  That is, it continues to use the configured Simple 
auth password, which can be null if it is never configured.  So, with 
that figured out, I am where Mark is, with Simple auth working.

Now, though, I have the problem where I can get search results OK, but 
if I double-click on one to open an editor view, GQ seg faults:

bash-2.05b# tail temp.txt
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "( 0.9.2342.19200300.100.1.21 NAM"..., 3815) = 3815
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "0\37\2\1\6e\32\n", 8)          = 8
read(6, "\1\0\4\23cn=schema,ou=system\4\0", 25) = 25
time(NULL)                              = 1102344652
brk(0)                                  = 0x8e9e000
brk(0x8ebf000)                          = 0x8ebf000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

This means very little to me, other than the fact that you did just 
recently enable schema publishing, and that last line appears related.

Same thing happens when I try to 'browse' to an entry:

bash-2.05b# tail -n 15 temp.txt
read(6, "( 2.5.4.5 NAME \'serialNumber\' DE"..., 19951) = 1674
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "( 2.5.4.39 NAME \'certificateRevo"..., 18277) = 5779
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "( 2.5.4.18 NAME \'postOfficeBox\' "..., 12498) = 9177
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "( 1.3.6.1.4.1.1466.115.121.1.20 "..., 3321) = 3321
select(1024, [6], [], NULL, NULL)       = 1 (in [6])
read(6, "0\37\2\1\7e\32\n", 8)          = 8
read(6, "\1\0\4\23cn=schema,ou=system\4\0", 25) = 25
time(NULL)                              = 1102344770
brk(0)                                  = 0x9f89000
brk(0x9faa000)                          = 0x9faa000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


-enrique

> 
> Alex
>