Re: dialog4ports crashing in head recently

2013-06-23 Thread Nathan Whitehorn

On 06/23/13 14:52, Dan Mack wrote:

dialog4ports has been crashing on all of my systems for about the last
week.  I rebuilt it with debug symbols and this is what I got (doesn't
matter which port is using it).

Anyone else seeing this?



libdialog was updated recently. I had to rebuild dialog4ports after that 
to keep it from crashing. Maybe you have the same issue?

-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: dialog4ports crashing in head recently

2013-06-23 Thread Peter Wemm
On Sun, Jun 23, 2013 at 1:36 PM, Nathan Whitehorn
nwhiteh...@freebsd.org wrote:
 On 06/23/13 14:52, Dan Mack wrote:

 dialog4ports has been crashing on all of my systems for about the last
 week.  I rebuilt it with debug symbols and this is what I got (doesn't
 matter which port is using it).

 Anyone else seeing this?


 libdialog was updated recently. I had to rebuild dialog4ports after that to
 keep it from crashing. Maybe you have the same issue?
 -Nathan

I've had the same problem on the freebsd.org cluster over the last
week or so.  A forced rebuild of dialog4ports solved it for me.

-- 
Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: dialog4ports crashing in head recently

2013-06-23 Thread Dan Mack
Yep, I'm running the latest ...

root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # pkg info | grep dialog
dialog4ports-0.1.5 Console Interface to configure ports

I originally thought it was just one system that was messed up having been
through so many generations of buildworld/installworld so this box (winbsd)
is a freshly installed like this:

 1.  installed a fresh VM guest with my release.iso from r251520
 2.  to get /usr/src, I built subversion from /usr/ports
 3.  step 2 probably built dialog4ports via portmaster automagically using
libdiag from r251420
 4.  after getting /usr/src and rebuilding current from head, dialog4ports
has the new crash behaviour.

I just tried Nathan and Peter's suggestion and it fixes the problem.  If
you have dialog4ports installed from an older release... about a week ago,
it needs to be rebuilt it appears.

Dan


On Sun, Jun 23, 2013 at 3:16 PM, Ilya A. Arkhipov rum1...@yandex.ru wrote:

 24.06.2013, 00:10, Dan Mack danm...@gmail.com:
  dialog4ports has been crashing on all of my systems for about the last
  week.  I rebuilt it with debug symbols and this is what I got (doesn't
  matter which port is using it).
 
  Anyone else seeing this?
 
  Dan
 
  root@winbsd:/usr/ports/net-mgmt # cd zabbix2-agent/
  root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # ls
  Makefile dialog4ports.core
  root@winbsd:/usr/ports/net-mgmt/zabbix2-agent # gdb `which dialog4ports`
  dialog4ports.core
  GNU gdb 6.1.1 [FreeBSD]
  Copyright 2004 Free Software Foundation, Inc.
  GDB is free software, covered by the GNU General Public License, and you
 are
  welcome to change it and/or distribute copies of it under certain
  conditions.
  Type show copying to see the conditions.
  There is absolutely no warranty for GDB.  Type show warranty for
 details.
  This GDB was configured as amd64-marcel-freebsd...
  Core was generated by `dialog4ports'.
  Program terminated with signal 6, Aborted.
  Reading symbols from /lib/libncursesw.so.8...done.
  Loaded symbols for /lib/libncursesw.so.8
  Reading symbols from /lib/libm.so.5...done.
  Loaded symbols for /lib/libm.so.5
  Reading symbols from /usr/lib/libdialog.so.7...done.
  Loaded symbols for /usr/lib/libdialog.so.7
  Reading symbols from /lib/libc.so.7...done.
  Loaded symbols for /lib/libc.so.7
  Reading symbols from /libexec/ld-elf.so.1...done.
  Loaded symbols for /libexec/ld-elf.so.1
  #0  0x000800fedffa in kill () from /lib/libc.so.7
  (gdb) where
  #0  0x000800fedffa in kill () from /lib/libc.so.7
  #1  0x000800f8c4c0 in __stack_chk_fail () from /lib/libc.so.7
  #2  0x000800f8c430 in __stack_chk_fail () from /lib/libc.so.7
  #3  0x004029aa in main (argc=value optimized out, argv=value
  optimized out) at dialog4ports.c:212
 
  --
 
   /*
* Dan Mack
* danmack at gmail.com
*/
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org

 Hi Dan,

 It is interesting because 212 line is:
 err(EXIT_FAILURE, List of items should not be empty);

 Have you last dialog4ports?(dialog4ports == 0.1.5)
 I doesn't have any problem with last ports/d4p.

 Can you also provide bt full output for me.

 --
 With Best Regards,
 Ilya A. Arkhipov




-- 

 /*
  * Dan Mack
  * danmack at gmail.com
  */
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: dialog4ports crashing in head recently

2013-06-23 Thread Konstantin Belousov
On Sun, Jun 23, 2013 at 01:53:24PM -0700, Peter Wemm wrote:
 On Sun, Jun 23, 2013 at 1:36 PM, Nathan Whitehorn
 nwhiteh...@freebsd.org wrote:
  On 06/23/13 14:52, Dan Mack wrote:
 
  dialog4ports has been crashing on all of my systems for about the last
  week.  I rebuilt it with debug symbols and this is what I got (doesn't
  matter which port is using it).
 
  Anyone else seeing this?
 
 
  libdialog was updated recently. I had to rebuild dialog4ports after that to
  keep it from crashing. Maybe you have the same issue?
  -Nathan
 
 I've had the same problem on the freebsd.org cluster over the last
 week or so.  A forced rebuild of dialog4ports solved it for me.

This means that the libdialog ABI was broken, right ?
If yes, the so version must be bumped.  This is the duty of the
committer, not re.


pgp_5wF7rtN23.pgp
Description: PGP signature