It's ok, the problem is that when NetBSD implemented strnvis they rather
stupidly changed the argument order and FreeBSD picked up the functions
from them. Please give the configure.ac change in my last mail a go.
Thanks
On Mon, Dec 02, 2013 at 07:51:17PM -0500, Eitan Adler wrote:
> On Mon, Dec
On Mon, Dec 2, 2013 at 6:55 PM, Nicholas Marriott
wrote:
> Honestly, you are not making this easy...
I'm sorry... I'm trying to provide what you are asking for; I supplied
*ent previously but will supply it again here.
gdb$ up
#1 0x000800fec57f in ?? () from /lib/libc.so.7
gdb$ up
#2 0x00
try this please, although i'm not sure if this is what i want to do at
least i'll know if it works
you'll need to rerun autogen.sh and then configure
diff --git a/configure.ac b/configure.ac
index ceb37db..644b283 100644
--- a/configure.ac
+++ b/configure.ac
@@ -312,6 +312,16 @@ AM_CONDITIONAL(NO
Never mind, looks like FreeBSD's strnvis argument order is different
from OpenBSD's, looking to see when that happened.
On Mon, Dec 02, 2013 at 11:55:32PM +, Nicholas Marriott wrote:
> Honestly, you are not making this easy...
>
> Could you just do "p *ent" and "p *code" from this frame in
Honestly, you are not making this easy...
Could you just do "p *ent" and "p *code" from this frame in gdb?
With -O0 you should hopefully see something like:
(gdb) p *ent
$1 = {code = TTYC_BEL, type = TTYCODE_STRING, name = 0x3c00cf68 "bel"}
(gdb) p *code
$2 = {type = TTYCODE_STRING, value = {str
On Mon, Dec 2, 2013 at 4:57 PM, Nicholas Marriott
wrote:
> yeah give that a try if you can
gdb$ p/x ent
$1 = 0x478030
gdb$ p/x *ent
$2 = {
code = 0x1,
type = 0x1,
name = 0x4789f0
}
(lldb) thread backtrace
* thread #1: tid = 0, 0x00080104a01b
libc.so.7`strlen(str=0x0050) + 1
yeah give that a try if you can
On Mon, Dec 02, 2013 at 04:52:50PM -0500, Eitan Adler wrote:
> On Mon, Dec 2, 2013 at 10:09 AM, Nicholas Marriott
> wrote:
> > I need to see inside the ent and code structures. Can you use gdb and
> > then do "p *ent" and "p *code" from frame 3? Or whatever frame i
On Mon, Dec 2, 2013 at 10:09 AM, Nicholas Marriott
wrote:
> I need to see inside the ent and code structures. Can you use gdb and
> then do "p *ent" and "p *code" from frame 3? Or whatever frame it shows
> is in cmd_server_info_exec.
gdb says "No symbol "ent" in current context."
lldb says (const
I need to see inside the ent and code structures. Can you use gdb and
then do "p *ent" and "p *code" from frame 3? Or whatever frame it shows
is in cmd_server_info_exec.
On Mon, Dec 02, 2013 at 09:52:19AM -0500, Eitan Adler wrote:
> On Mon, Dec 2, 2013 at 3:52 AM, Nicholas Marriott
> wrote:
> >
On Mon, Dec 2, 2013 at 3:52 AM, Nicholas Marriott
wrote:
> Show me "bt full" from gdb please
gdb761$ bt full
#0 strlen (str=0x50 ) at
/usr/src/lib/libc/string/strlen.c:100
lp =
va =
vb =
p =
#1 0x000800fc657f in istrsenvisx (mbdst=0x7fffafd0 "",
dlen=
Also please go to frame 3 (in cmd_server_info_exec) and show me "p *ent"
and "p *code".
On Sun, Dec 01, 2013 at 11:31:09PM -0500, Eitan Adler wrote:
> Hi all,
>
> I can reproducibly crash tmux by doing "tmux info".
>
> Debugging information follows. Please let me know if I can provide
> anythi
Show me "bt full" from gdb please
Original message
From: Eitan Adler
Date: 02/12/2013 04:31 (GMT+00:00)
To: tmux-users@lists.sourceforge.net
Subject: Segfault when doing "tmux info"
Hi all,
I can reproducibly crash tmux by doing "tmux info".
Debugging information follo
12 matches
Mail list logo
