Re: Seg Faults building devel/gobject-inspection with latest 8.0_BETA

[D'Arcy Cain]

On 06/22/17 17:19, Joerg Sonnenberger wrote:

On Wed, Jun 21, 2017 at 06:25:26PM -0400, D'Arcy Cain wrote:

On 06/21/17 17:02, D'Arcy Cain wrote:

On 06/21/17 11:04, D'Arcy Cain wrote:

#0  0x70e05a605663 in ?? ()
#1  0x70e05a200585 in ?? () from /usr/pkg/lib/libgthread-2.0.so.0
#2  0x70e0665e9b60 in ?? ()
#3  0x70e05a200669 in _fini () from /usr/pkg/lib/libgthread-2.0.so.0
#4  0x in ?? ()

I am deleting glib2 and dependents and trying again.


Same thing.  Rebuilding everything with symbols to further debug.


Well, I half expected this.  I built with symbols and it didn't dump core.
Now what?


Can you check if libgthread exports any symbols from libgcc? I wonder
if that is where the problem comes from...


You're a bit above my pay grade.  I understand what you are suggesting 
but I am not sure how to check.


By the way, I added this to my mk,conf:

MKSTRIPSYM=no
MKDEBUG=YES
INSTALL_UNSTRIPPED=YES

But I still get the exact same backtrace from gdb.

--
D'Arcy J.M. Cain 
http://www.NetBSD.org/ IM:da...@vex.net

Re: Seg Faults building devel/gobject-inspection with latest 8.0_BETA

[Joerg Sonnenberger]

On Wed, Jun 21, 2017 at 06:25:26PM -0400, D'Arcy Cain wrote:
> On 06/21/17 17:02, D'Arcy Cain wrote:
> > On 06/21/17 11:04, D'Arcy Cain wrote:
> > > #0  0x70e05a605663 in ?? ()
> > > #1  0x70e05a200585 in ?? () from /usr/pkg/lib/libgthread-2.0.so.0
> > > #2  0x70e0665e9b60 in ?? ()
> > > #3  0x70e05a200669 in _fini () from /usr/pkg/lib/libgthread-2.0.so.0
> > > #4  0x in ?? ()
> > > 
> > > I am deleting glib2 and dependents and trying again.
> > 
> > Same thing.  Rebuilding everything with symbols to further debug.
> 
> Well, I half expected this.  I built with symbols and it didn't dump core.
> Now what?

Can you check if libgthread exports any symbols from libgcc? I wonder
if that is where the problem comes from...

Joerg

Re: Seg Faults building devel/gobject-inspection with latest 8.0_BETA

[Roy Marples]

On 21/06/2017 23:25, D'Arcy Cain wrote:

On 06/21/17 17:02, D'Arcy Cain wrote:

On 06/21/17 11:04, D'Arcy Cain wrote:

#0  0x70e05a605663 in ?? ()
#1  0x70e05a200585 in ?? () from /usr/pkg/lib/libgthread-2.0.so.0
#2  0x70e0665e9b60 in ?? ()
#3  0x70e05a200669 in _fini () from /usr/pkg/lib/libgthread-2.0.so.0
#4  0x in ?? ()

I am deleting glib2 and dependents and trying again.


Same thing.  Rebuilding everything with symbols to further debug.


Well, I half expected this.  I built with symbols and it didn't dump 
core.  Now what?


Pretty sure this is a toolchain issue.
I solved this by using clang instead of gcc - yes I realise it's not 
everyone's idea of a fix.


Roy

Re: Automated report: NetBSD-current/i386 build failure

[Kamil Rytarowski]

On 22.06.2017 17:11, NetBSD Test Fixture wrote:
> This is an automatically generated notice of a NetBSD-current/i386
> build failure.
> 
> The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
> using sources from CVS date 2017.06.22.13.42.09.
> 
> An extract from the build.sh output follows:
> 
>   ^
> --- dependall-external ---
> --- dependall-acpica ---
> /tmp/bracket/build/2017.06.22.13.42.09-i386/tools/bin/nbctfconvert -g -L 
> VERSION aslhelp.o
> --- dependall-bin ---
> /tmp/bracket/build/2017.06.22.13.42.09-i386/src/bin/ksh/emacs.c:2174:2: 
> error: #endif without #if
>  #endif /* EDIT */
>   ^
> nbmkdep: compile failed.
> *** [emacs.d] Error code 1
> nbmake[6]: stopped in 
> /tmp/bracket/build/2017.06.22.13.42.09-i386/src/bin/ksh
> --- dependall-external ---
> 
> The following commits were made between the last successful build and
> the failed build:
> 

Fixed. I applied wrong patch.




signature.asc
Description: OpenPGP digital signature

revival of pc532 which used port-pc532@ )

[Julian H. Stacey]

Hi NetBSD people
Old public hardware architecture PC532 first ran Minix, Mach, then NetBSD
& had 2 lists pc...@bungi.com & port-pc...@netbsd.org both lists dead now.
New + old people are focusing looking to maybe make
more PCBs, re-assemble old code inc PLA Eproms, boot disks, assembly
ICs, & contact people who may need/ donate/ sell/ buy components
or complete PC532 machines.  If you know people who had a PC532,
or bits, please forward to them, Thanks.

Please don't reply to me privately, join new list & reply there, Thanks:
http://mailman.berklix.org/mailman/listinfo/pc532

Cheers,
Julian
-- 
Julian Stacey, Computer Consultant, BSD Linux Unix Systems Engineer
 Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
 http://berklix.eu/brexit/#700k_stolen_votes