Re: Mark www/vimb broken

2018-07-25 Thread Leonid Bobrov
Issue closed, it finally runs at my broken laptop.



Re: Mark www/vimb broken

2018-07-19 Thread Leonid Bobrov
From lan...@openbsd.org Thu Jul 19 09:16:39 2018

On Thu, Jul 19, 2018 at 12:42:45AM +0300, Leonid Bobrov wrote:
> This is what I get at latest snapshot at amd64:
> https://transfer.sh/gnUY6/vimb.mpg

You've been told to use ktrace or LD_DEBUG=1 to figure out what happens
in your environment. Something is wrong *in your environment*, as vimb
works for other people. Posting a screen capture like this isnt helpful,
as you're asking ppl to do your homework.

Landry


LD_DEBUG output is not clear (there is a useless spam I am unable to
copy because it is so long that tmux doesn't scroll up to the beginning)
this all what I see when the GUI stops working:
free tib=0x1a73b4bb4600
tib new=0x1a7433e63000
tib new=0x1a748c5de400

ktrace.out is 14.5M big, so I am not sure it is a good idea to attach it
directly in mail: https://transfer.sh/Mqb9Y/ktrace.out

And GDB output:
mazocomp$ egdb vimb
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-openbsd6.3".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from vimb...done.
(gdb) run
Starting program: /usr/local/bin/vimb
[New process 25947]
[New process 25947]
[New process 25947]
[New thread 222575]
[New thread 212795]
[New thread 340723]
[New thread 388577]
[New thread 452316]
[New thread 401452]
[New thread 584335]

Thread 1 received signal SIGUSR1, User defined signal 1.
_thread_sys_poll () at -:3
3   -: No such file or directory.
(gdb) bt
#0  _thread_sys_poll () at -:3
#1  0x139e2f33dffe in _libc_poll_cancel (fds=0x139d610ca2a0, nfds=3, 
timeout=1827315591) at /usr/src/lib/libc/sys/w_poll.c:27
#2  0x139e2885bc37 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at 
gmain.c:4204
#3  g_main_context_iterate (context=, block=, 
dispatch=, self=) at gmain.c:3898
#4  0x139e2885c08f in g_main_loop_run (loop=0x139e4449cdd0) at gmain.c:4099
#5  0x139e0e26be08 in gtk_main () at gtkmain.c:1323
#6  0x139b52608936 in main (argc=, argv=) at 
main.c:1986
(gdb) bt full
#0  _thread_sys_poll () at -:3
No locals.
#1  0x139e2f33dffe in _libc_poll_cancel (fds=0x139d610ca2a0, nfds=3, 
timeout=1827315591) at /usr/src/lib/libc/sys/w_poll.c:27
_tib = 0x139d9d7cd140
#2  0x139e2885bc37 in g_main_context_poll (priority=0, context=, timeout=, fds=, n_fds=) at 
gmain.c:4204
ret = 
errsv = 
poll_func = 0x139e2886cfa0 
#3  g_main_context_iterate (context=, block=, 
dispatch=, self=) at gmain.c:3898
fds = 0x139d610ca2a0
allocated_nfds = 3
max_priority = 
nfds = 3
timeout = 1827315591
some_ready = 
#4  0x139e2885c08f in g_main_loop_run (loop=0x139e4449cdd0) at gmain.c:4099
No locals.
#5  0x139e0e26be08 in gtk_main () at gtkmain.c:1323
loop = 0x139e4449cdd0
#6  0x139b52608936 in main (argc=, argv=) at 
main.c:1986
opts = {{long_name = 0x139b5271ea9a "embed", short_name = 101 'e', 
flags = 0, arg = G_OPTION_ARG_STRING, arg_data = 0x7f7e3508, description = 
0x139b5271eaa0 "Reparents to window specified by xid",
arg_description = 0x0}, {long_name = 0x139b5271eac5 "config", 
short_name = 99 'c', flags = 0, arg = G_OPTION_ARG_FILENAME, arg_data = 
0x139b52829110 ,
description = 0x139b5271eacc "Custom configuration file", 
arg_description = 0x0}, {long_name = 0x139b5271eae6 "profile", short_name = 112 
'p', flags = 0, arg = G_OPTION_ARG_CALLBACK,
arg_data = 0x139b52608a80 , description = 
0x139b5271eaee "Profile name", arg_description = 0x0}, {long_name = 
0x139b5271eb01 "version", short_name = 118 'v', flags = 0,
arg = G_OPTION_ARG_NONE, arg_data = 0x7f7e3504, description = 
0x139b5271eafb "Print version", arg_description = 0x0}, {long_name = 
0x139b5271eb09 "bug-info", short_name = 0 '\000', flags = 0,
arg = G_OPTION_ARG_NONE, arg_data = 0x7f7e3500, description = 
0x139b5271eb12 "Print used library versions", arg_description = 0x0}, 
{long_name = 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE,
arg_data = 0x0, description = 0x0, arg_description = 0x0}}
ver = 
buginfo = 
winid = 
err = 
pidstr = 
c = 0x139e455fe260
(gdb)



Re: Mark www/vimb broken

2018-07-18 Thread Landry Breuil
On Thu, Jul 19, 2018 at 12:42:45AM +0300, Leonid Bobrov wrote:
> This is what I get at latest snapshot at amd64:
> https://transfer.sh/gnUY6/vimb.mpg

You've been told to use ktrace or LD_DEBUG=1 to figure out what happens
in your environment. Something is wrong *in your environment*, as vimb
works for other people. Posting a screen capture like this isnt helpful,
as you're asking ppl to do your homework.

Landry



Re: Mark www/vimb broken

2018-07-18 Thread Leonid Bobrov
This is what I get at latest snapshot at amd64:
https://transfer.sh/gnUY6/vimb.mpg



Re: Mark www/vimb broken

2018-07-17 Thread Leonid Bobrov
From: Rafael Sadowski 

On Tue Jul 17, 2018 at 01:55:42AM -0400, Brian Callahan wrote:
> 
> On 07/17/18 00:46, Leonid Bobrov wrote:
> > Hi!
> > 
> > After recent snapshot updates I'm no longer able to use this port,
> > not sure this is problem of port update, because I was able to use
> > 3.2.0 before updating snaphot. When I start this browser, I have to
> > wait one minute and it stops responding, I can't even kill it using
> > CM-x in CWM.
> 
> It works fine here on the latest snapshot and package set.

Same here on amd64.

> 
> ~Brian
> 
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/www/vimb/Makefile,v
> > retrieving revision 1.16
> > diff -u -p -u -p -r1.16 Makefile
> > --- Makefile27 Jun 2018 21:04:06 -  1.16
> > +++ Makefile17 Jul 2018 04:39:14 -
> > @@ -1,11 +1,13 @@
> >   # $OpenBSD: Makefile,v 1.16 2018/06/27 21:04:06 espie Exp $
> > +BROKEN =   not responding at runtime
> > +
> >   COMMENT = modal webkit-based browser inspired by vim
> >   GH_ACCOUNT =  fanglingsu
> >   GH_PROJECT =  vimb
> >   GH_TAGNAME =  3.2.0
> > -REVISION = 0
> > +REVISION = 1
> >   CATEGORIES =  www x11
> > 
> 


This is weird, I'm running latest snapshot on amd64, after I removed
files generated by Vimb in my home directory, it still doesn't respond
at runtime. Other browsers based on www/webkitgtk4 run fine.



Re: Mark www/vimb broken

2018-07-17 Thread Rafael Sadowski
On Tue Jul 17, 2018 at 01:55:42AM -0400, Brian Callahan wrote:
> 
> On 07/17/18 00:46, Leonid Bobrov wrote:
> > Hi!
> > 
> > After recent snapshot updates I'm no longer able to use this port,
> > not sure this is problem of port update, because I was able to use
> > 3.2.0 before updating snaphot. When I start this browser, I have to
> > wait one minute and it stops responding, I can't even kill it using
> > CM-x in CWM.
> 
> It works fine here on the latest snapshot and package set.

Same here on amd64.

> 
> ~Brian
> 
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/www/vimb/Makefile,v
> > retrieving revision 1.16
> > diff -u -p -u -p -r1.16 Makefile
> > --- Makefile27 Jun 2018 21:04:06 -  1.16
> > +++ Makefile17 Jul 2018 04:39:14 -
> > @@ -1,11 +1,13 @@
> >   # $OpenBSD: Makefile,v 1.16 2018/06/27 21:04:06 espie Exp $
> > +BROKEN =   not responding at runtime
> > +
> >   COMMENT = modal webkit-based browser inspired by vim
> >   GH_ACCOUNT =  fanglingsu
> >   GH_PROJECT =  vimb
> >   GH_TAGNAME =  3.2.0
> > -REVISION = 0
> > +REVISION = 1
> >   CATEGORIES =  www x11
> > 
> 



Re: Mark www/vimb broken

2018-07-16 Thread Brian Callahan



On 07/17/18 00:46, Leonid Bobrov wrote:

Hi!

After recent snapshot updates I'm no longer able to use this port,
not sure this is problem of port update, because I was able to use
3.2.0 before updating snaphot. When I start this browser, I have to
wait one minute and it stops responding, I can't even kill it using
CM-x in CWM.


It works fine here on the latest snapshot and package set.

~Brian


Index: Makefile
===
RCS file: /cvs/ports/www/vimb/Makefile,v
retrieving revision 1.16
diff -u -p -u -p -r1.16 Makefile
--- Makefile27 Jun 2018 21:04:06 -  1.16
+++ Makefile17 Jul 2018 04:39:14 -
@@ -1,11 +1,13 @@
  # $OpenBSD: Makefile,v 1.16 2018/06/27 21:04:06 espie Exp $
  
+BROKEN =	not responding at runtime

+
  COMMENT = modal webkit-based browser inspired by vim
  
  GH_ACCOUNT =	fanglingsu

  GH_PROJECT =  vimb
  GH_TAGNAME =  3.2.0
-REVISION = 0
+REVISION = 1
  
  CATEGORIES =	www x11
  





Mark www/vimb broken

2018-07-16 Thread Leonid Bobrov
Hi!

After recent snapshot updates I'm no longer able to use this port,
not sure this is problem of port update, because I was able to use
3.2.0 before updating snaphot. When I start this browser, I have to
wait one minute and it stops responding, I can't even kill it using
CM-x in CWM.

Index: Makefile
===
RCS file: /cvs/ports/www/vimb/Makefile,v
retrieving revision 1.16
diff -u -p -u -p -r1.16 Makefile
--- Makefile27 Jun 2018 21:04:06 -  1.16
+++ Makefile17 Jul 2018 04:39:14 -
@@ -1,11 +1,13 @@
 # $OpenBSD: Makefile,v 1.16 2018/06/27 21:04:06 espie Exp $
 
+BROKEN =   not responding at runtime
+
 COMMENT =  modal webkit-based browser inspired by vim
 
 GH_ACCOUNT =   fanglingsu
 GH_PROJECT =   vimb
 GH_TAGNAME =   3.2.0
-REVISION = 0
+REVISION = 1
 
 CATEGORIES =   www x11