From bug-notifications at lists.opencsw.org Mon Feb 2 11:44:58 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Mon, 2 Feb 2015 11:44:58 +0100 Subject: [netsnmp 0005229]: default log path not included in package -> no logging output produced Message-ID: <1cfe3897492c2296417796e1c9b16506@www.opencsw.org> The following issue has been SUBMITTED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5229 ====================================================================== Reported By: hjb Assigned To: ====================================================================== Project: netsnmp Issue ID: 5229 Category: packaging Reproducibility: always Severity: trivial Priority: normal Status: new ====================================================================== Date Submitted: 2015-02-02 11:44 CET Last Modified: 2015-02-02 11:44 CET ====================================================================== Summary: default log path not included in package -> no logging output produced Description: Looks like the netsnmp has been built with a default log file setting of: /var/opt/csw/log/snmpd.log But the directory /var/opt/csw/log isn't created during installation of netsnmp. After manually creating it, snmpd' log messages start to appear in the mentioned default log file. ====================================================================== From bug-notifications at lists.opencsw.org Mon Feb 9 10:49:25 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Mon, 9 Feb 2015 10:49:25 +0100 Subject: [apache24 0005212]: substitution error in generating httpd.conf In-Reply-To: Message-ID: <3257b74396f6cf98162ab58d0a1dc4f8@www.opencsw.org> The following issue has been ASSIGNED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5212 ====================================================================== Reported By: davidrlinn Assigned To: dam ====================================================================== Project: apache24 Issue ID: 5212 Category: Reproducibility: have not tried Severity: minor Priority: normal Status: assigned ====================================================================== Date Submitted: 2014-10-17 23:55 CEST Last Modified: 2015-02-09 10:49 CET ====================================================================== Summary: substitution error in generating httpd.conf Description: The distributed httpd.conf file has several strings containing "//opt/csw". These appear to be the result of substituting "/opt/csw" into places where "opt/csw" might have been a better choice. apache24 2.4.7,REV=2014.02.21 ====================================================================== From bug-notifications at lists.opencsw.org Tue Feb 10 12:44:32 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Tue, 10 Feb 2015 12:44:32 +0100 Subject: [apache24 0005212]: substitution error in generating httpd.conf In-Reply-To: Message-ID: <89c3a4a5a18dd0caca19c7822977506e@www.opencsw.org> The following issue has been CLOSED ====================================================================== https://www.opencsw.org/mantis/view.php?id=5212 ====================================================================== Reported By: davidrlinn Assigned To: dam ====================================================================== Project: apache24 Issue ID: 5212 Category: Reproducibility: have not tried Severity: minor Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2014-10-17 23:55 CEST Last Modified: 2015-02-10 12:44 CET ====================================================================== Summary: substitution error in generating httpd.conf Description: The distributed httpd.conf file has several strings containing "//opt/csw". These appear to be the result of substituting "/opt/csw" into places where "opt/csw" might have been a better choice. apache24 2.4.7,REV=2014.02.21 ====================================================================== ---------------------------------------------------------------------- (0011014) dam (administrator) - 2015-02-10 12:44 https://www.opencsw.org/mantis/view.php?id=5212#c11014 ---------------------------------------------------------------------- This is fixed in REV=2015.02.10, thanks for the report! From bug-notifications at lists.opencsw.org Tue Feb 10 12:45:11 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Tue, 10 Feb 2015 12:45:11 +0100 Subject: [apache24 0005224]: apache24 cannot start with smf due wrong env CONF_FILE in svc-cswapache24 method In-Reply-To: <4dd0e374b74e2f75d8b26883fa1959b1> Message-ID: <2a5a0c8d78bba11bf0fab0af614aaec5@www.opencsw.org> The following issue has been CLOSED ====================================================================== https://www.opencsw.org/mantis/view.php?id=5224 ====================================================================== Reported By: Bastian Assigned To: dam ====================================================================== Project: apache24 Issue ID: 5224 Category: Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2015-01-04 23:07 CET Last Modified: 2015-02-10 12:45 CET ====================================================================== Summary: apache24 cannot start with smf due wrong env CONF_FILE in svc-cswapache24 method Description: After installation fresh CSWapache24 i found it came to maintanance mode right away. The reason is that service cannot start becouse in /var/opt/csw/svc/method there is wrong config file pathname pointing to the non existing localization: CONF_FILE=/etc/opt/csw/apache24/httpd.conf it should be CONF_FILE=/etc/opt/csw/apache2/httpd.conf After that service starts without problem. Since this si apache24 i suggest change the directory name to apache24 instead of changing patchname in method file. ====================================================================== ---------------------------------------------------------------------- (0011015) dam (administrator) - 2015-02-10 12:45 https://www.opencsw.org/mantis/view.php?id=5224#c11015 ---------------------------------------------------------------------- This is fixed in REV=2015.02.10, probably earlier. From bug-notifications at lists.opencsw.org Wed Feb 11 13:28:52 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 11 Feb 2015 13:28:52 +0100 Subject: [puppet3 0005150]: Report does not work In-Reply-To: <796cb1d8dec969939263add158e80944> Message-ID: <9696076d5b74df257c6663e696944ba8@www.opencsw.org> A NOTE has been added to this issue. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5150 ====================================================================== Reported By: vavhab Assigned To: tosmi ====================================================================== Project: puppet3 Issue ID: 5150 Category: Reproducibility: always Severity: minor Priority: normal Status: feedback ====================================================================== Date Submitted: 2014-02-11 18:30 CET Last Modified: 2015-02-11 13:28 CET ====================================================================== Summary: Report does not work Description: Report does not work: Notice: Finished catalog run in 0.26 seconds Debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) Debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml Error: Could not send report: Error 406 on SERVER: Not Acceptable: No supported formats are acceptable (Accept: b64_zlib_yaml, yaml, raw) It says preferred_serialization_format pson is invalid, it should be valid. Thanks, ====================================================================== ---------------------------------------------------------------------- (0011016) tosmi (manager) - 2015-02-11 13:28 https://www.opencsw.org/mantis/view.php?id=5150#c11016 ---------------------------------------------------------------------- closing this issue because of -ENOFEEDBACK From bug-notifications at lists.opencsw.org Wed Feb 11 13:30:10 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 11 Feb 2015 13:30:10 +0100 Subject: [puppet3 0005150]: Report does not work In-Reply-To: <796cb1d8dec969939263add158e80944> Message-ID: The following issue has been CLOSED ====================================================================== https://www.opencsw.org/mantis/view.php?id=5150 ====================================================================== Reported By: vavhab Assigned To: tosmi ====================================================================== Project: puppet3 Issue ID: 5150 Category: Reproducibility: always Severity: minor Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2014-02-11 18:30 CET Last Modified: 2015-02-11 13:30 CET ====================================================================== Summary: Report does not work Description: Report does not work: Notice: Finished catalog run in 0.26 seconds Debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) Debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml Error: Could not send report: Error 406 on SERVER: Not Acceptable: No supported formats are acceptable (Accept: b64_zlib_yaml, yaml, raw) It says preferred_serialization_format pson is invalid, it should be valid. Thanks, ====================================================================== ---------------------------------------------------------------------- (0011017) tosmi (manager) - 2015-02-11 13:30 https://www.opencsw.org/mantis/view.php?id=5150#c11017 ---------------------------------------------------------------------- because of no feedback provided. please try the latest puppet packages from opencsw. From bug-notifications at lists.opencsw.org Thu Feb 12 14:09:50 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Thu, 12 Feb 2015 14:09:50 +0100 Subject: [netsnmp 0005229]: default log path not included in package -> no logging output produced In-Reply-To: <5b1931c340026683eb593cc3ed6cbfc7> Message-ID: <0c579da6d1a44c8038bf008f6eef3672@www.opencsw.org> The following issue has been ASSIGNED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5229 ====================================================================== Reported By: hjb Assigned To: cgrzemba ====================================================================== Project: netsnmp Issue ID: 5229 Category: packaging Reproducibility: always Severity: trivial Priority: normal Status: assigned ====================================================================== Date Submitted: 2015-02-02 11:44 CET Last Modified: 2015-02-12 14:09 CET ====================================================================== Summary: default log path not included in package -> no logging output produced Description: Looks like the netsnmp has been built with a default log file setting of: /var/opt/csw/log/snmpd.log But the directory /var/opt/csw/log isn't created during installation of netsnmp. After manually creating it, snmpd' log messages start to appear in the mentioned default log file. ====================================================================== From bug-notifications at lists.opencsw.org Thu Feb 12 14:10:31 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Thu, 12 Feb 2015 14:10:31 +0100 Subject: [netsnmp 0005229]: default log path not included in package -> no logging output produced In-Reply-To: <5b1931c340026683eb593cc3ed6cbfc7> Message-ID: The following issue has been CLOSED ====================================================================== https://www.opencsw.org/mantis/view.php?id=5229 ====================================================================== Reported By: hjb Assigned To: cgrzemba ====================================================================== Project: netsnmp Issue ID: 5229 Category: packaging Reproducibility: always Severity: trivial Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2015-02-02 11:44 CET Last Modified: 2015-02-12 14:10 CET ====================================================================== Summary: default log path not included in package -> no logging output produced Description: Looks like the netsnmp has been built with a default log file setting of: /var/opt/csw/log/snmpd.log But the directory /var/opt/csw/log isn't created during installation of netsnmp. After manually creating it, snmpd' log messages start to appear in the mentioned default log file. ====================================================================== ---------------------------------------------------------------------- (0011018) cgrzemba (manager) - 2015-02-12 14:10 https://www.opencsw.org/mantis/view.php?id=5229#c11018 ---------------------------------------------------------------------- contained in 5.7.2,REV=2015.02.12 From bug-notifications at lists.opencsw.org Thu Feb 12 15:30:09 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Thu, 12 Feb 2015 15:30:09 +0100 Subject: [openssh_client 0005230]: manpage of ssh-copy-id is broken on Solaris Message-ID: <4332f325d31cf1b8075916aa189f3eb4@www.opencsw.org> The following issue has been SUBMITTED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5230 ====================================================================== Reported By: dam Assigned To: ====================================================================== Project: openssh_client Issue ID: 5230 Category: regular use Reproducibility: always Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2015-02-12 15:30 CET Last Modified: 2015-02-12 15:30 CET ====================================================================== Summary: manpage of ssh-copy-id is broken on Solaris Description: buildbot at buildbot [buildbot]:~/ansible > man ssh-copy-id Reformatting page. Please Wait... done is a script that uses to log into a remote machine (presumably using a login password, so password authentication should be enabled, unless you've done some clever use of multiple identi- ties). It assembles a list of one or more fingerprints (as described below) and tries to log in with each key, to see if any ... Probably mdoc2man.awk should be applied to convert it. ====================================================================== From bug-notifications at lists.opencsw.org Wed Feb 18 09:28:29 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 18 Feb 2015 09:28:29 +0100 Subject: [gdb 0005231]: gcore dumps core when trying to get core from running process Message-ID: <301b3880cd1919dc190b6cbf311de954@www.opencsw.org> The following issue has been SUBMITTED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5231 ====================================================================== Reported By: hjb Assigned To: ====================================================================== Project: gdb Issue ID: 5231 Category: regular use Reproducibility: always Severity: crash Priority: normal Status: new ====================================================================== Date Submitted: 2015-02-18 09:28 CET Last Modified: 2015-02-18 09:28 CET ====================================================================== Summary: gcore dumps core when trying to get core from running process Description: Using the gcore binary provided in the CSWgdb package to get a core image of a running process doesn't work - the written corefile is zero byte size. Instead gcore itself dumps a core :) See this example: root at ulysses# echo $BASH /usr/bin/bash root at ulysses# /opt/csw/bin/gcore $$ [New process 20121] Retry https://www.opencsw.org/mantis/view.php?id=1: Retry https://www.opencsw.org/mantis/view.php?id=2: Retry https://www.opencsw.org/mantis/view.php?id=3: Retry https://www.opencsw.org/mantis/view.php?id=4: 0xff14d4d8 in ?? () procfs.c:5523: internal-error: procfs_make_note_section: Assertion `thread_args.note_data != note_data' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] procfs.c:5523: internal-error: procfs_make_note_section: Assertion `thread_args.note_data != note_data' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Abort - core dumped root at ulysses# ls -ltrh | tail -2 -rw-r--r-- 1 root root 0 Feb 18 09:21 core.20121 -rw------- 1 root root 8.9M Feb 18 09:21 core root at ulysses# pstack core core 'core' of 11673: /opt/csw/bin/sparcv9/gdb --nx --batch -ex set pagination off -ex set h ffffffff7f1daf1c _lwp_kill (6, 0, ffffffff7f1b9a94, ffffffffffffffff, ffffffff7f33c000, 0) + 8 ffffffff7f14b310 abort (1, 1d8, 0, 1f0dfc, 0, 0) + 118 000000010025c8c4 ???????? (1, 1005f8e20, 1003cb8e0, ffffffff7eb0b7a8, 0, 6) 000000010025eea0 ???????? (100538570, 100338858, 1005f8e20, 1, 1003cc3b8, 100400) 000000010025ef24 internal_verror (100338858, 1593, 100338838, ffffffff7fffedb8, 400, 100563088) + 20 000000010025ef6c internal_error (100338858, 1593, 100338838, 1003397a0, 100338868, 6) + 20 0000000100062c8c ???????? (1005f8c30, ffffffff7ffff07c, 0, 100561000, 1005fe340, 1005fe340) 00000001002896b0 write_gcore_file (1005f8c30, 1005f8c30, ffffffff7ffffb3b, a, 1002c9bdc, 1005f8c30) + 34 00000001002899a8 ???????? (1005e9f10, 0, 1005e9f40, 100400, 1005f8c30, 1005fb620) 0000000100096dc0 ???????? (1005daf60, ffffffff7ffffb31, 0, 1, ffffffff7ffff160, 1005daf60) 0000000100099234 cmd_func (1005daf60, ffffffff7ffffb31, 0, 80808080, ff00, 80808080) + 14 000000010025a1a8 execute_command (ffffffff7ffffb2b, 0, 1005e9f70, 1003762c8, ffffffff7ffffb31, 1005daf60) + 2c8 0000000100179b78 catch_command_errors (100259ee0, ffffffff7ffffb2b, 0, 6, 0, 2) + 50 000000010017cfc0 ???????? (0, 100259ee0, 10009e2f4, 1005400a0, 100400, 4) 0000000100179a88 catch_errors (1, ffffffff7ffff7b0, 100393888, 6, 1c00, 0) + 68 000000010017d9c0 gdb_main (1, 0, ffffffff7f348240, ffffffff7f349e44, ffffffff7f400200, 10053b458) + 40 000000010033304c main (11, ffffffff7ffff888, ffffffff7ffff918, 100563088, 100000000, ffffffff7f400200) + 28 00000001000536d4 _start (0, 0, 0, 0, 0, 0) + 7c ====================================================================== From bug-notifications at lists.opencsw.org Wed Feb 18 09:38:32 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 18 Feb 2015 09:38:32 +0100 Subject: [gdb 0005232]: gdb can't read core file Message-ID: The following issue has been SUBMITTED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5232 ====================================================================== Reported By: hjb Assigned To: ====================================================================== Project: gdb Issue ID: 5232 Category: regular use Reproducibility: always Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 2015-02-18 09:38 CET Last Modified: 2015-02-18 09:38 CET ====================================================================== Summary: gdb can't read core file Description: The provided gdb isn't able to read core files. Here's an example: root at ulysses# echo $BASH /usr/bin/bash root at ulysses# /usr/bin/gcore $$ gcore: core.20121 dumped root at ulysses# file core.20121 core.20121: ELF 32-bit MSB core file SPARC Version 1, from 'bash' root at ulysses# /opt/csw/bin/gdb /usr/bin/bash core.20121 GNU gdb (GDB) 7.7 Copyright (C) 2014 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 "sparc-sun-solaris2.10". 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 /usr/bin/bash...(no debugging symbols found)...done. warning: Couldn't find general-purpose registers in core file. warning: Wrong size fpregset in core file. [Thread debugging using libthread_db enabled] [New Thread 1 (LWP 1)] Core was generated by `-bash'. warning: Couldn't find general-purpose registers in core file. warning: Wrong size fpregset in core file. PC not available #-1 in ?? () (gdb) Let's compare that with this really old gdb i've got from sunfreeware years ago, iirc: root at ulysses# ./gdb /usr/bin/bash core.20121 GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.10"...(no debugging symbols found)... Core was generated by `-bash'. Reading symbols from /lib/libcurses.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcurses.so.1 Reading symbols from /lib/libsocket.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libsocket.so.1 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libdl.so.1... warning: Lowest section in /lib/libdl.so.1 is .hash at 000000b4 (no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.1 Reading symbols from /lib/libc.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.1 Reading symbols from /platform/sun4v/lib/libc_psr.so.1...(no debugging symbols found)...done. Loaded symbols for /platform/SUNW,SPARC-Enterprise-T5120/lib/libc_psr.so.1 https://www.opencsw.org/mantis/view.php?id=0 0x00000000 in ?? () (gdb) ====================================================================== From bug-notifications at lists.opencsw.org Wed Feb 18 18:38:59 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 18 Feb 2015 18:38:59 +0100 Subject: [gdb 0005231]: gcore dumps core when trying to get core from running process In-Reply-To: <7eb0170f38840d894caf65c706f8db36> Message-ID: The following issue has been ASSIGNED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5231 ====================================================================== Reported By: hjb Assigned To: pfelecan ====================================================================== Project: gdb Issue ID: 5231 Category: regular use Reproducibility: always Severity: crash Priority: normal Status: assigned ====================================================================== Date Submitted: 2015-02-18 09:28 CET Last Modified: 2015-02-18 18:38 CET ====================================================================== Summary: gcore dumps core when trying to get core from running process Description: Using the gcore binary provided in the CSWgdb package to get a core image of a running process doesn't work - the written corefile is zero byte size. Instead gcore itself dumps a core :) See this example: root at ulysses# echo $BASH /usr/bin/bash root at ulysses# /opt/csw/bin/gcore $$ [New process 20121] Retry https://www.opencsw.org/mantis/view.php?id=1: Retry https://www.opencsw.org/mantis/view.php?id=2: Retry https://www.opencsw.org/mantis/view.php?id=3: Retry https://www.opencsw.org/mantis/view.php?id=4: 0xff14d4d8 in ?? () procfs.c:5523: internal-error: procfs_make_note_section: Assertion `thread_args.note_data != note_data' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] procfs.c:5523: internal-error: procfs_make_note_section: Assertion `thread_args.note_data != note_data' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] Abort - core dumped root at ulysses# ls -ltrh | tail -2 -rw-r--r-- 1 root root 0 Feb 18 09:21 core.20121 -rw------- 1 root root 8.9M Feb 18 09:21 core root at ulysses# pstack core core 'core' of 11673: /opt/csw/bin/sparcv9/gdb --nx --batch -ex set pagination off -ex set h ffffffff7f1daf1c _lwp_kill (6, 0, ffffffff7f1b9a94, ffffffffffffffff, ffffffff7f33c000, 0) + 8 ffffffff7f14b310 abort (1, 1d8, 0, 1f0dfc, 0, 0) + 118 000000010025c8c4 ???????? (1, 1005f8e20, 1003cb8e0, ffffffff7eb0b7a8, 0, 6) 000000010025eea0 ???????? (100538570, 100338858, 1005f8e20, 1, 1003cc3b8, 100400) 000000010025ef24 internal_verror (100338858, 1593, 100338838, ffffffff7fffedb8, 400, 100563088) + 20 000000010025ef6c internal_error (100338858, 1593, 100338838, 1003397a0, 100338868, 6) + 20 0000000100062c8c ???????? (1005f8c30, ffffffff7ffff07c, 0, 100561000, 1005fe340, 1005fe340) 00000001002896b0 write_gcore_file (1005f8c30, 1005f8c30, ffffffff7ffffb3b, a, 1002c9bdc, 1005f8c30) + 34 00000001002899a8 ???????? (1005e9f10, 0, 1005e9f40, 100400, 1005f8c30, 1005fb620) 0000000100096dc0 ???????? (1005daf60, ffffffff7ffffb31, 0, 1, ffffffff7ffff160, 1005daf60) 0000000100099234 cmd_func (1005daf60, ffffffff7ffffb31, 0, 80808080, ff00, 80808080) + 14 000000010025a1a8 execute_command (ffffffff7ffffb2b, 0, 1005e9f70, 1003762c8, ffffffff7ffffb31, 1005daf60) + 2c8 0000000100179b78 catch_command_errors (100259ee0, ffffffff7ffffb2b, 0, 6, 0, 2) + 50 000000010017cfc0 ???????? (0, 100259ee0, 10009e2f4, 1005400a0, 100400, 4) 0000000100179a88 catch_errors (1, ffffffff7ffff7b0, 100393888, 6, 1c00, 0) + 68 000000010017d9c0 gdb_main (1, 0, ffffffff7f348240, ffffffff7f349e44, ffffffff7f400200, 10053b458) + 40 000000010033304c main (11, ffffffff7ffff888, ffffffff7ffff918, 100563088, 100000000, ffffffff7f400200) + 28 00000001000536d4 _start (0, 0, 0, 0, 0, 0) + 7c ====================================================================== From bug-notifications at lists.opencsw.org Wed Feb 18 18:39:22 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 18 Feb 2015 18:39:22 +0100 Subject: [gdb 0005232]: gdb can't read core file In-Reply-To: Message-ID: <19dd4766184764ccecfd0677546cf6d9@www.opencsw.org> The following issue has been ASSIGNED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5232 ====================================================================== Reported By: hjb Assigned To: pfelecan ====================================================================== Project: gdb Issue ID: 5232 Category: regular use Reproducibility: always Severity: major Priority: normal Status: assigned ====================================================================== Date Submitted: 2015-02-18 09:38 CET Last Modified: 2015-02-18 18:39 CET ====================================================================== Summary: gdb can't read core file Description: The provided gdb isn't able to read core files. Here's an example: root at ulysses# echo $BASH /usr/bin/bash root at ulysses# /usr/bin/gcore $$ gcore: core.20121 dumped root at ulysses# file core.20121 core.20121: ELF 32-bit MSB core file SPARC Version 1, from 'bash' root at ulysses# /opt/csw/bin/gdb /usr/bin/bash core.20121 GNU gdb (GDB) 7.7 Copyright (C) 2014 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 "sparc-sun-solaris2.10". 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 /usr/bin/bash...(no debugging symbols found)...done. warning: Couldn't find general-purpose registers in core file. warning: Wrong size fpregset in core file. [Thread debugging using libthread_db enabled] [New Thread 1 (LWP 1)] Core was generated by `-bash'. warning: Couldn't find general-purpose registers in core file. warning: Wrong size fpregset in core file. PC not available #-1 in ?? () (gdb) Let's compare that with this really old gdb i've got from sunfreeware years ago, iirc: root at ulysses# ./gdb /usr/bin/bash core.20121 GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.10"...(no debugging symbols found)... Core was generated by `-bash'. Reading symbols from /lib/libcurses.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libcurses.so.1 Reading symbols from /lib/libsocket.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libsocket.so.1 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libdl.so.1... warning: Lowest section in /lib/libdl.so.1 is .hash at 000000b4 (no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.1 Reading symbols from /lib/libc.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.1 Reading symbols from /platform/sun4v/lib/libc_psr.so.1...(no debugging symbols found)...done. Loaded symbols for /platform/SUNW,SPARC-Enterprise-T5120/lib/libc_psr.so.1 https://www.opencsw.org/mantis/view.php?id=0 0x00000000 in ?? () (gdb) ====================================================================== From bug-notifications at lists.opencsw.org Tue Feb 24 15:12:03 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Tue, 24 Feb 2015 15:12:03 +0100 Subject: [libkrb5_3 0005233]: ssh fails with error with "ld.so.1: ./ssh: fatal: libkrb5.so.3: open failed: No such file or directory" Message-ID: The following issue has been SUBMITTED. ====================================================================== https://www.opencsw.org/mantis/view.php?id=5233 ====================================================================== Reported By: tm17 Assigned To: ====================================================================== Project: libkrb5_3 Issue ID: 5233 Category: packaging Reproducibility: have not tried Severity: major Priority: normal Status: new ====================================================================== Date Submitted: 2015-02-24 15:12 CET Last Modified: 2015-02-24 15:12 CET ====================================================================== Summary: ssh fails with error with "ld.so.1: ./ssh: fatal: libkrb5.so.3: open failed: No such file or directory" Description: This is a follow up to issue 4992. The "fix" applied by the reporter (tampering with LD_NOVERSION) isn't very helpful in general. The remark "I just pushed the updated 1.9.2,REV=2012.08.23 krb5_lib packages to unstable/." by dam (2012-09-17 16:56) looks much more promising, if only I were able to find that version on unstable (or stable). What is the status of that version? ====================================================================== From bug-notifications at lists.opencsw.org Wed Feb 25 01:14:24 2015 From: bug-notifications at lists.opencsw.org (Mantis Bug Tracker via bug-notifications) Date: Wed, 25 Feb 2015 01:14:24 +0100 Subject: [python 0003054]: Add 64-bit support In-Reply-To: Message-ID: A NOTE has been added to this issue. ====================================================================== https://www.opencsw.org/mantis/view.php?id=3054 ====================================================================== Reported By: harpchad Assigned To: maciej ====================================================================== Project: python Issue ID: 3054 Category: packaging Reproducibility: always Severity: feature Priority: normal Status: assigned ====================================================================== Date Submitted: 2009-02-02 20:00 CET Last Modified: 2015-02-25 01:14 CET ====================================================================== Summary: Add 64-bit support Description: Need a 64-bit libpython for dependent packages. ====================================================================== ---------------------------------------------------------------------- (0011019) maciej (administrator) - 2015-02-25 01:14 https://www.opencsw.org/mantis/view.php?id=3054#c11019 ---------------------------------------------------------------------- Upstream bug: http://bugs.python.org/issue18083