Re: [sparc64] sudo command causes a bus error

[Frans van Berckel]

On Thu, 2011-09-08 at 20:24 +0200, Julien Cristau wrote:

> You need to build the package with debug symbols (usually setting
> DEB_BUILD_OPTIONS=nostrip in the build environment works), then run gdb
> on that binary to get more useful information.  Bus error most likely
> means unaligned access, so you'll have to figure out where that comes
> from.
> 
> Cheers,
> Julien

The sudo package created on sparc64-port with debug nostrip option on.

root@deblnxsrv254:~# gdb /usr/bin/sudo
GNU gdb (GDB) 7.3-debian

This GDB was configured as "sparc64-linux-gnu".

Reading symbols from /usr/bin/sudo...done.

(gdb) r
Starting program: /usr/bin/sudo 

Program received signal SIGBUS, Bus error.
0xf801008e0420 in make_grlist_item 
(user=, gids=, ngids=1)
at /usr/src/sudo-1.8.2/plugins/sudoers/pwutil.c:552
552 grlist->groups[ngroups++] = cp;

Thanks,


Frans van Berckel



-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1315515976.5134.12.ca...@deblnxsrv222.lan

Re: [sparc64] sudo command causes a bus error

[Julien Cristau]

On Thu, Sep  8, 2011 at 11:41:54 +0200, Frans van Berckel wrote:

> root@deblnxsrv254:~# gdb /usr/bin/sudo   
> GNU gdb (GDB) 7.3-debian
> Copyright (C) 2011 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 "sparc64-linux-gnu".
> For bug reporting instructions, please see:
> ...
> Reading symbols from /usr/bin/sudo...(no debugging symbols
> found)...done.
> 
> (gdb) r
> Starting program: /usr/bin/sudo 
> 
> Program received signal SIGBUS, Bus error.
> 0xf801008e0220 in ?? () from /usr/lib/sudo/sudoers.so
> 
> Why is sudoers.so going true it knies? Do I need to build the package my
> selfs and run some tests? Or do you know what goes on?
> 
You need to build the package with debug symbols (usually setting
DEB_BUILD_OPTIONS=nostrip in the build environment works), then run gdb
on that binary to get more useful information.  Bus error most likely
means unaligned access, so you'll have to figure out where that comes
from.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110908182415.ga5...@radis.liafa.jussieu.fr

Re: libedit.so.2: cannot open shared object file

[Frans van Berckel]

On Thu, 2011-09-08 at 16:12 +0200, Aurelien Jarno wrote:
> 
> I have filled bug#640919 with a patch, fixing this issue, as well as a
> powerpc issue.

Aurelien,

Thanks, I just installed the new libedit2 package from debian-ports. Did
you build pmake outside of the buildd? It's available in the repro true.

Frans van Berckel


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1315501936.4419.8.ca...@deblnxsrv222.lan

Re: libedit.so.2: cannot open shared object file

[Aurelien Jarno]

On Sun, Sep 04, 2011 at 12:09:56PM +1000, Aníbal Monsalve Salazar wrote:
> On Fri, Sep 02, 2011 at 10:43:48AM +0200, Frans van Berckel wrote:
> >On Thu, 2011-09-01 at 20:36 +0200, Julien Cristau wrote:
> >>On Thu, Sep  1, 2011 at 18:27:37 +0200, Frans van Berckel wrote:
> >>
> >>>On Thu, 2011-09-01 at 15:59 +0200, Josip Rodin wrote:
> On Thu, Sep 01, 2011 at 10:15:23AM +0200, Frans van Berckel wrote:
> >>>
> >So I found the installed libedit2_2.11-20080614-3_sparc64 package is
> >only symbolic linking, but does not holds the libedit.so.2.11 it selfs.
> 
> Well, try find the build log for the package on sparc64 and see how it
> managed to build a package without error but also without a proper 
> result? :)
> >>>
> >>>Okay comparing the sparc64 and s390x log files. The source of both are
> >>>the same. The first diff I have found.
> >>>
> >>>*This is what sparc64 does.*
> >>>building standard edit library
> >>>ranlib libedit.a
> >>>all ===> readline
> >>>touch build-stamp
> >>
> >>Looks like a bug in pmake:
> >>
> >>NOPIC   Do not build PIC versions of system libraries, and
> >>do not build shared libraries.  [set if ${MACHINE_ARCH}
> >>is "sparc64", unset otherwise.]
> >>
> >>That might make sense on NetBSD, it certainly doesn't on Debian.
> >
> >It's not that clear to me what they exactly do in the bsd.own.mk patch
> >for all the different architectures. But this a sparc64-only part.
> >
> >+# The sparc64 port is incomplete.
> >+.if ${MACHINE_ARCH} == "sparc64"
> >+NOPROFILE=1
> >+NOPIC=1
> >+NOLINT=1
> >+.endif
> >
> >Who is able to write a understanding bug report?
> 
> Perhaps Guillem or Aurelien?
> 
> Hopefully with a patch. :)
> 

I have filled bug#640919 with a patch, fixing this issue, as well as a
powerpc issue.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110908141226.gd11...@hall.aurel32.net

[sparc64] sudo command causes a bus error

[Frans van Berckel]

Good to know - calling sudo in sid, causes a bus error on a
sparc64-ports setup.

root@deblnxsrv254:~# sudo
Bus error

root@deblnxsrv254:~# gdb /usr/bin/sudo   
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 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 "sparc64-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/sudo...(no debugging symbols
found)...done.

(gdb) r
Starting program: /usr/bin/sudo 

Program received signal SIGBUS, Bus error.
0xf801008e0220 in ?? () from /usr/lib/sudo/sudoers.so

Why is sudoers.so going true it knies? Do I need to build the package my
selfs and run some tests? Or do you know what goes on?

The Debian bug post, with more information, is available here ...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640304

Thanks,


Frans van Berckel


-- 
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1315474918.1742.11.ca...@deblnxsrv222.lan