[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Porting man-db to Hurd

On Tue, May 07, 2002 at 06:40:22PM +0200, Wolfgang Jährling wrote:
> Wolfgang Jährling <wolfgang@pro-linux.de> wrote:
> > Grant Bowman <grantbow@grantbow.com> wrote:
> > > [machine freeze-up]
> > 
> > Funny, I tried it and got a segmentation fault instead of a freeze. I'll
> > look into it in more detail later.
> It seems I did something wrong last time. But this time, I got the
> expected behaviour: The program just hung. "ps" told me that it's
> sleeping, so obviously memset() got tired, see this full backtrace:
> ----- snip! -----
> (gdb) bt full
> #0  0x010c67a1 in memset () from /lib/libc.so.0.3
> No symbol table info available.
> #1  0x011a108b in __bam_read_root () from /lib/libdb2.so.2
> No symbol table info available.
> #2  0x011a0e61 in __bam_open () from /lib/libdb2.so.2
> No symbol table info available.

That looks remarkably like #111288/#139962 in libdb2, although it's
previously only been reported on sparc.

If anybody cares to try to debug that, I'm sure Matthew would appreciate
it - I don't have the skills to dig into db2. For what it's worth,
man-db will be switching to libdb3 soon anyway.

> Doesn't look like mandb is doing anything wrong here.

I agree - or, at least, if it is, nobody has managed to point out
exactly what yet! :)

Colin Watson                                  [cjwatson@flatline.org.uk]

To UNSUBSCRIBE, email to debian-hurd-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: