Re: possible bug in libXt or libXaw

2014-11-16 Thread Marco Atzeri
On 11/16/2014 10:14 AM, Mark Geisert wrote: Marco Atzeri writes: On 11/16/2014 7:30 AM, Mark Geisert wrote: Marco Atzeri writes: this is the pointer causing the segfault (gdb) p form->form.horiz_base $2 = (Widget) 0x6275705f6779632f while similar pointers have a much smaller address, (gdb)

Re: possible bug in libXt or libXaw

2014-11-16 Thread Mark Geisert
Marco Atzeri writes: > On 11/16/2014 7:30 AM, Mark Geisert wrote: > > Marco Atzeri writes: > >> this is the pointer causing the segfault > >> > >> (gdb) p form->form.horiz_base > >> $2 = (Widget) 0x6275705f6779632f > >> > >> while similar pointers have a much smaller address, > >> > >> (gdb) p w >

Re: possible bug in libXt or libXaw

2014-11-15 Thread Marco Atzeri
On 11/16/2014 7:30 AM, Mark Geisert wrote: Marco Atzeri writes: this is the pointer causing the segfault (gdb) p form->form.horiz_base $2 = (Widget) 0x6275705f6779632f while similar pointers have a much smaller address, (gdb) p w $5 = (Widget) 0x60014bd50 so it that an assignment not clear

Re: possible bug in libXt or libXaw

2014-11-15 Thread Mark Geisert
Marco Atzeri writes: > this is the pointer causing the segfault > > (gdb) p form->form.horiz_base > $2 = (Widget) 0x6275705f6779632f > > while similar pointers have a much smaller address, > > (gdb) p w > $5 = (Widget) 0x60014bd50 > > so it that an assignment not clearing the upper > portion of

possible bug in libXt or libXaw

2014-11-15 Thread Marco Atzeri
testing ncview http://meteora.ucsd.edu/~pierce/ncview_home_page.html I found, only on 64 bit, a segfault due to incorrect widget (aka pointer) value. It could be a software bug, but it looks to me more a bug somewhere in the underlying libs #0 LayoutChild (w=w@entry=0x60014bd50) at /usr/src