Portinstall/upgrade stops with no error

Michael C. Shultz ringworm01 at gmail.com
Sun Mar 13 05:47:17 PST 2005


On Sunday 13 March 2005 02:36 am, Doug Lee wrote:
> On Sat, Mar 12, 2005 at 03:24:19PM -0800, Michael C. Shultz wrote:
> > Portmanager is at version 0.2.9_2 now so you should update with
> > cvsup.  I'm guessing you did not run portmanager as root, if that
> > is the problem the current version will correctly report it.
> >
> > -Mike
> >
> > Yes I ran it as root (hence the "#" in "Kirk 3#"), but I'm now
> > doing a cvsup of ports and will try an upgrade of portmanager
> > anyway.
>
> If it still cores, build with WITH_DEBUG=yes and send me the core
> please if you are on a X86 system. If not the output of
> gdb /usr/local/bin/portmanager ./portmanager.core
> bt
> would be very helpful.  Thanks
>
> -Mike
>
> Built with debug, still cores.  gdb output first:
>
> (gdb) bt
> #0  0x280d5b74 in strstr () from /usr/lib/libc.so.4
> #1  0x2806f7a0 in PMGRrAddDependencies (property=0xbfbff5b4,
>     portName=0x804e1b0 "pine-4.44") at PMGRrAddDependencies.c:109
> #2  0x2806fca6 in PMGRrDbCreate (property=0xbfbff5b4) at
> PMGRrDbCreate.c:173 #3  0x280746ff in PMGRrStatus
> (property=0xbfbff5b4) at PMGRrStatus.c:53 #4  0x8049137 in
> PMGRrShowLeaves () at PMGRrShowLeaves.c:26
> #5  0x8048a44 in PMGRrShowLeaves () at PMGRrShowLeaves.c:26
> #6  0x8048986 in PMGRrShowLeaves () at PMGRrShowLeaves.c:26
> (gdb) f 1
> #1  0x2806f7a0 in PMGRrAddDependencies (property=0xbfbff5b4,
>     portName=0x804e1b0 "pine-4.44") at PMGRrAddDependencies.c:109
> 109			stringSize			= strstr( portDependencyDir, "\n" ) -
> portDependencyDir; (gdb) print portDependency
> $1 = 0x8050049 "cclient-2001a,1"
> (gdb)
>
> Core size 417 K.  If you need it, I'll email it privately.  I doubt
> there's anything compromising in there...

This back trace is very helpful, from it I should be able to find the 
problem so thanks!

If your machine is a X86 class machine then sending the core file would 
make things even easier, also the output of uname -a would be nice.  On 
first glance I am suspicious of the /var/db/pkg/pine-4.44/+CONTENTS 
file, it maybe corrupt on your system  but I need to install pine and 
check it out on my system first.  Even if there is something wrong with 
pine on your system portmanager should be printing an error message and 
not core dumping.   I certainly have a bug to fix on this end so thanks 
for reporting this!

I'll keep you informed on the progress with fixing this.

-Mike
 



More information about the freebsd-questions mailing list