from:"Tony Reix"

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

** Attachment added: "hs_err_pid26910.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096211/+files/hs_err_pid26910.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] [NEW] fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04

$ uname -a
Linux tony1 3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:13 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux

$ apt-cache policy openjdk-7-jre-lib
openjdk-7-jre-lib:
  Installed: 7u51-2.4.6-1ubuntu4
  Candidate: 7u51-2.4.6-1ubuntu4
  Version table:
 *** 7u51-2.4.6-1ubuntu4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/universe ppc64el 
Packages
100 /var/lib/dpkg/status

$ apt-cache policy openjdk-7-jre
openjdk-7-jre:
  Installed: 7u51-2.4.6-1ubuntu4
  Candidate: 7u51-2.4.6-1ubuntu4
  Version table:
 *** 7u51-2.4.6-1ubuntu4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
100 /var/lib/dpkg/status

$ apt-cache policy openjdk-7-jdk
openjdk-7-jdk:
  Installed: 7u51-2.4.6-1ubuntu4
  Candidate: 7u51-2.4.6-1ubuntu4
  Version table:
 *** 7u51-2.4.6-1ubuntu4 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
100 /var/lib/dpkg/status


I'm running Hadoop 2.4.0 tests on Ubuntu 14.04 on PPC64-LE .
I've run about 4 times the Hadoop 2.4.0 tests and got 7 cores, 3 with Java6 
(6.0_30-b30) and now 4 with Java7 (7.0_51-b31).
Before Hadoop 2.4.0 , I was testing Hadoop 2.2.0 and got only 1 core 
(1.7.0_51-b31) with more tests runs.
I'm compiling/testing Hadoop without Hadoop JNI code ( no -Dnative option).
I've put the ulimit at some time and got 1 (big) core file.

All five Java7 cores look the same:
- appearing in:
   hadoop-hdfs-project/hadoop-hdfs
- dealing with:
Current thread (.):  JavaThread "FSImageSaver for :
  
/home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name2
  
/home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1

However, the cores made different Hadoop tests to crash.
Running several times all the Hadoop tests shown that JVM crashes are random: 
the same elementary test may crash the JVM or run perfectly or output a Failure 
when run several times.


hadoop-hdfs-project/hadoop-hdfs/hs_err_pid7832.log  :

# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (os_linux_zero.cpp:254), pid=7832, tid=70365657166240
#  fatal error: caught unhandled signal 11
#
# JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-b31)
# Java VM: OpenJDK 64-Bit Zero VM (24.51-b03 interpreted mode linux-ppc64le )

---  T H R E A D  ---

Current thread (0x3fff946fdee0):  JavaThread "FSImageSaver for
/home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-
hdfs/target/test/data/dfs/name1 of type IMAGE_AND_EDITS"
[_thread_in_Java, id=7843, stack(0x3fff47e6,0x3fff4800)]

Stack: [0x3fff47e6,0x3fff4800],  sp=0x3fff47f353e0,
free space=852k

** Affects: openjdk-7 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

Here are4 hs*.log files produced when JVM7 crashed.

** Attachment added: "hs_err_pid7832.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096210/+files/hs_err_pid7832.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

** Attachment added: "hs_err_pid8407.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096213/+files/hs_err_pid8407.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

** Attachment added: "hs_err_pid32470.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096212/+files/hs_err_pid32470.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-04-25 Thread Tony Reix

** Changed in: openjdk-7 (Ubuntu)
 Assignee: (unassigned) => Tony Reix (tony-reix)

** Changed in: openjdk-7 (Ubuntu)
   Status: New => Invalid

** Description changed:

- $ lsb_release -rd
- Description:  Ubuntu 14.04 LTS
- Release:  14.04
- 
- $ uname -a
- Linux tony1 3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:13 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
- 
- $ apt-cache policy openjdk-7-jre-lib
- openjdk-7-jre-lib:
-   Installed: 7u51-2.4.6-1ubuntu4
-   Candidate: 7u51-2.4.6-1ubuntu4
-   Version table:
-  *** 7u51-2.4.6-1ubuntu4 0
- 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/universe ppc64el 
Packages
- 100 /var/lib/dpkg/status
- 
- $ apt-cache policy openjdk-7-jre
- openjdk-7-jre:
-   Installed: 7u51-2.4.6-1ubuntu4
-   Candidate: 7u51-2.4.6-1ubuntu4
-   Version table:
-  *** 7u51-2.4.6-1ubuntu4 0
- 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
- 100 /var/lib/dpkg/status
- 
- $ apt-cache policy openjdk-7-jdk
- openjdk-7-jdk:
-   Installed: 7u51-2.4.6-1ubuntu4
-   Candidate: 7u51-2.4.6-1ubuntu4
-   Version table:
-  *** 7u51-2.4.6-1ubuntu4 0
- 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
- 100 /var/lib/dpkg/status
- 
- 
- I'm running Hadoop 2.4.0 tests on Ubuntu 14.04 on PPC64-LE .
- I've run about 4 times the Hadoop 2.4.0 tests and got 7 cores, 3 with Java6 
(6.0_30-b30) and now 4 with Java7 (7.0_51-b31).
- Before Hadoop 2.4.0 , I was testing Hadoop 2.2.0 and got only 1 core 
(1.7.0_51-b31) with more tests runs.
- I'm compiling/testing Hadoop without Hadoop JNI code ( no -Dnative option).
- I've put the ulimit at some time and got 1 (big) core file.
- 
- All five Java7 cores look the same:
- - appearing in:
-hadoop-hdfs-project/hadoop-hdfs
- - dealing with:
- Current thread (.):  JavaThread "FSImageSaver for :
-   
/home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name2
-   
/home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1
- 
- However, the cores made different Hadoop tests to crash.
- Running several times all the Hadoop tests shown that JVM crashes are random: 
the same elementary test may crash the JVM or run perfectly or output a Failure 
when run several times.
- 
- 
- hadoop-hdfs-project/hadoop-hdfs/hs_err_pid7832.log  :
- 
- # A fatal error has been detected by the Java Runtime Environment:
- #
- #  Internal Error (os_linux_zero.cpp:254), pid=7832, tid=70365657166240
- #  fatal error: caught unhandled signal 11
- #
- # JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-b31)
- # Java VM: OpenJDK 64-Bit Zero VM (24.51-b03 interpreted mode linux-ppc64le )
- 
- ---  T H R E A D  ---
- 
- Current thread (0x3fff946fdee0):  JavaThread "FSImageSaver for
- /home/tony/HADOOP/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-
- hdfs/target/test/data/dfs/name1 of type IMAGE_AND_EDITS"
- [_thread_in_Java, id=7843, stack(0x3fff47e6,0x3fff4800)]
- 
- Stack: [0x3fff47e6,0x3fff4800],  sp=0x3fff47f353e0,
- free space=852k
+ Invalid.

** Attachment removed: "hs_err_pid7832.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096210/+files/hs_err_pid7832.log

** Attachment removed: "hs_err_pid26910.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096211/+files/hs_err_pid26910.log

** Attachment removed: "hs_err_pid32470.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096212/+files/hs_err_pid32470.log

** Attachment removed: "hs_err_pid8407.log"
   
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+attachment/4096213/+files/hs_err_pid8407.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1312598] Re: fatal error: caught unhandled signal 11

2014-05-14 Thread Tony Reix

Hi.
I opened this defect in the wrong world. So, I made it invalid and opened 
1312623.
Sorry for the confusion.
Tony

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312598

Title:
  fatal error: caught unhandled signal 11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1312598/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-18 Thread Tony Reix

Here is the list of v1.55 errors that appear on PPC64LE and not on
Intel64:

- Memory Access Violation:
  
libs/math/test/test_jacobi.test/gcc-4.8/debug/link-static/test_jacobi.output

- Cores:
  libs/log/test/core.test/gcc-4.8/debug/build-no/threading-multi/core
  libs/phoenix/test/core.test/gcc-4.8/debug/core
139 
libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output
139 
libs/coroutine/test/test_coroutine.test/gcc-4.8/debug/link-static/test_coroutine.output

- Other errors:
1 
libs/multiprecision/test/test_arithmetic_ab_1.test/gcc-4.8/debug/test_arithmetic_ab_1.output
1 
libs/multiprecision/test/test_arithmetic_backend_concept.test/gcc-4.8/debug/test_arithmetic_backend_concept.output
1 
libs/multiprecision/test/test_arithmetic_cpp_dec_float_2.test/gcc-4.8/debug/test_arithmetic_cpp_dec_float_2.output
1 
libs/multiprecision/test/test_arithmetic_cpp_dec_float_3.test/gcc-4.8/debug/test_arithmetic_cpp_dec_float_3.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_10.test/gcc-4.8/debug/test_arithmetic_cpp_int_10.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_11.test/gcc-4.8/debug/test_arithmetic_cpp_int_11.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_12.test/gcc-4.8/debug/test_arithmetic_cpp_int_12.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_13.test/gcc-4.8/debug/test_arithmetic_cpp_int_13.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_16.test/gcc-4.8/debug/test_arithmetic_cpp_int_16.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_1.test/gcc-4.8/debug/test_arithmetic_cpp_int_1.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_2.test/gcc-4.8/debug/test_arithmetic_cpp_int_2.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_4.test/gcc-4.8/debug/test_arithmetic_cpp_int_4.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_5.test/gcc-4.8/debug/test_arithmetic_cpp_int_5.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_7.test/gcc-4.8/debug/test_arithmetic_cpp_int_7.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_8.test/gcc-4.8/debug/test_arithmetic_cpp_int_8.output
1 
libs/multiprecision/test/test_arithmetic_cpp_int_9.test/gcc-4.8/debug/test_arithmetic_cpp_int_9.output
1 
libs/multiprecision/test/test_arithmetic_dbg_adptr2.test/gcc-4.8/debug/test_arithmetic_dbg_adptr2.output
1 
libs/multiprecision/test/test_arithmetic_logged_2.test/gcc-4.8/debug/test_arithmetic_logged_2.output
1 
libs/spirit/test/qi_regression_numeric_alternatives-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_regression_numeric_alternatives-p3.output

201 
libs/conversion/test/lexical_cast_float_types_test.test/gcc-4.8/debug/link-static/lexical_cast_float_types_test.output
201 
libs/conversion/test/lexical_cast_inf_nan_test.test/gcc-4.8/debug/link-static/lexical_cast_inf_nan_test.output
201 
libs/conversion/test/lexical_cast_loopback_test.test/gcc-4.8/debug/link-static/lexical_cast_loopback_test.output
201 libs/geometry/test/algorithms/area.test/gcc-4.8/debug/area.output
201 libs/geometry/test/algorithms/centroid.test/gcc-4.8/debug/centroid.output
201 
libs/geometry/test/algorithms/difference.test/gcc-4.8/debug/difference.output
201 libs/geometry/test/algorithms/expand.test/gcc-4.8/debug/expand.output
201 
libs/geometry/test/algorithms/intersection.test/gcc-4.8/debug/intersection.output
201 
libs/geometry/test/algorithms/overlay/ccw_traverse.test/gcc-4.8/debug/ccw_traverse.output
201 
libs/geometry/test/algorithms/overlay/get_turns.test/gcc-4.8/debug/get_turns.output
201 
libs/geometry/test/algorithms/overlay/self_intersection_points.test/gcc-4.8/debug/self_intersection_points.output
201 
libs/geometry/test/algorithms/overlay/traverse.test/gcc-4.8/debug/traverse.output
201 libs/geometry/test/algorithms/union.test/gcc-4.8/debug/union.output
201 libs/geometry/test/algorithms/within.test/gcc-4.8/debug/within.output
201 
libs/geometry/test/multi/algorithms/multi_difference.test/gcc-4.8/debug/multi_difference.output
201 
libs/geometry/test/multi/algorithms/multi_intersection.test/gcc-4.8/debug/multi_intersection.output
201 
libs/geometry/test/multi/algorithms/multi_union.test/gcc-4.8/debug/multi_union.output
201 
libs/math/test/log1p_expm1_test.test/gcc-4.8/debug/link-static/log1p_expm1_test.output
201 
libs/math/test/powm1_sqrtp1m1_test.test/gcc-4.8/debug/link-static/powm1_sqrtp1m1_test.output
201 libs/math/test/pow_test.test/gcc-4.8/debug/link-static/pow_test.output
201 libs/math/test/test_airy.test/gcc-4.8/debug/link-static/test_airy.output
201 
libs/math/test/test_bessel_airy_zeros.test/gcc-4.8/debug/link-static/test_bessel_airy_zeros.output
201 
libs/math/test/test_bessel_i.test/gcc-4.8/debug/link-static/test_bessel_i.output
201 
libs/math/test/test_bessel_j.test/gcc-4.8/debug/link-static/test_bessel_j.output
201 
libs/math/test/test_bessel_k.test/gcc-4.8/debug/link-static/test_bessel_k.output
201 
libs/math/test/test_bessel_y.test/gcc-4.8/debug/link-static/test_bessel_y.output
201 libs/ma

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-18 Thread Tony Reix

I forgot to talk again about the tests running an infinite loop on
PPC64, that never appear on AMD64:

Here are infinite loops on PPC64-BE (I provide the last trace appearing
on the screen. The blocking test is: test_tr1* that I killed) :

gcc.link 
../bin.v2/libs/math/test/test_tr1.test/gcc-4.8.2/debug/link-static/test_tr1
gcc.link 
../bin.v2/libs/math/test/test_tr1_long_double.test/gcc-4.8.2/debug/link-static/test_tr1_long_double
gcc.link 
../bin.v2/libs/math/test/test_tr1_c.test/gcc-4.8.2/debug/link-static/test_tr1_c
gcc.link 
../bin.v2/libs/math/test/test_tr1_c_long_double.test/gcc-4.8.2/debug/link-static/test_tr1_c_long_double
./bin.v2/libs/math/test/test_bessel_y.test/gcc-4.8.2/debug/link-static/test_bessel_y


Here are infinite loops on PPC64-LE:

gcc.link 
../bin.v2/libs/math/test/test_ellint_1.test/gcc-4.8/debug/link-static/test_ellint_1
gcc.link 
../bin.v2/libs/math/test/test_ellint_2.test/gcc-4.8/debug/link-static/test_ellint_2
gcc.link 
../bin.v2/libs/math/test/test_ellint_2.test/gcc-4.8/debug/link-static/test_ellint_3


Anyway, it also seems that there are MANY tests failures about the Math library 
on PPC64.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-19 Thread Tony Reix

Here are the results of testing Boost 1.55 on Fedora 19 on PPC/BE.

4380 tests

libs/heap/test/pairing_heap_tests.test/gcc-4.8.2/debug/threading-multi/pairing_heap_tests.output
libs/heap/test/mutable_heap_test.test/gcc-4.8.2/debug/threading-multi/mutable_heap_test.output
libs/heap/test/d_ary_heap_test.test/gcc-4.8.2/debug/threading-multi/d_ary_heap_test.output
libs/heap/test/fibonacci_heap_test.test/gcc-4.8.2/debug/threading-multi/fibonacci_heap_test.output
libs/heap/test/skew_heap_test.test/gcc-4.8.2/debug/threading-multi/skew_heap_test.output
libs/heap/test/priority_queue_test.test/gcc-4.8.2/debug/threading-multi/priority_queue_test.output
libs/heap/test/binomial_heap_test.test/gcc-4.8.2/debug/threading-multi/binomial_heap_test.output
libs/math/test/test_jacobi.test/gcc-4.8.2/debug/link-static/test_jacobi.output
Number of Memory Access Violation:  8

Possible Exit Status:  0 1 134 137 139 200 201

  0 4243
  1   15
1341
1379
1394
2009
201   98
-
Tot 4380
Err  137
%Pass 96.87
Dif1

Number of sub-failures:  47171

Cores:
./libs/phoenix/test/core.test/gcc-4.8.2/debug/core
./libs/log/test/core.test/gcc-4.8.2/debug/build-no/threading-multi/core

  1 
libs/spirit/repository/test/qi_repo_keywords.test/gcc-4.8.2/debug/qi_repo_keywords.output
  1 
libs/spirit/test/karma_binary1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary1-p3.output
  1 
libs/spirit/test/qi_regression_numeric_alternatives-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_regression_numeric_alternatives-p3.output
  1 
libs/spirit/test/qi_binary-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_binary-p3.output
  1 
libs/spirit/test/karma_alternative1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_alternative1-p3.output
134 
libs/spirit/test/qi_match_manip1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_match_manip1-p3.output
  1 
libs/spirit/test/karma_binary3-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary3-p3.output
  1 
libs/spirit/test/qi_regression_stream_eof-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_regression_stream_eof-p3.output
  1 
libs/spirit/test/qi_int1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_int1-p3.output
  1 
libs/spirit/test/karma_binary2-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary2-p3.output
  1 
libs/spirit/test/karma_real2-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_real2-p3.output
  1 
libs/spirit/test/karma_real1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_real1-p3.output
139 
libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8.2/debug/phoenix_v3-on/lex_lexertl2-p3.output
200 
libs/heap/test/pairing_heap_tests.test/gcc-4.8.2/debug/threading-multi/pairing_heap_tests.output
200 
libs/heap/test/mutable_heap_test.test/gcc-4.8.2/debug/threading-multi/mutable_heap_test.output
200 
libs/heap/test/d_ary_heap_test.test/gcc-4.8.2/debug/threading-multi/d_ary_heap_test.output
200 
libs/heap/test/fibonacci_heap_test.test/gcc-4.8.2/debug/threading-multi/fibonacci_heap_test.output
200 
libs/heap/test/skew_heap_test.test/gcc-4.8.2/debug/threading-multi/skew_heap_test.output
200 
libs/heap/test/priority_queue_test.test/gcc-4.8.2/debug/threading-multi/priority_queue_test.output
200 
libs/heap/test/binomial_heap_test.test/gcc-4.8.2/debug/threading-multi/binomial_heap_test.output
139 
libs/coroutine/test/test_coroutine.test/gcc-4.8.2/debug/link-static/test_coroutine.output
139 
libs/filesystem/test/operations_test_static.test/gcc-4.8.2/debug/link-static/operations_test_static.output
201 libs/tr1/test/std_run_random.test/gcc-4.8.2/debug/std_run_random.output
201 libs/tr1/test/run_random.test/gcc-4.8.2/debug/run_random.output
  1 
libs/wave/test/build/testwave.test/gcc-4.8.2/debug/link-static/threading-multi/testwave.output
137 
libs/math/example/bessel_zeros_example_1.test/gcc-4.8.2/debug/bessel_zeros_example_1.output
201 
libs/math/test/test_hypergeometric_dist2.test/gcc-4.8.2/debug/link-static/test_hypergeometric_dist2.output
201 
libs/math/test/test_igamma.test/gcc-4.8.2/debug/link-static/test_igamma.output
201 
libs/math/test/test_policy_sf.test/gcc-4.8.2/debug/link-static/test_policy_sf.output
201 libs/math/test/test_erf.test/gcc-4.8.2/debug/link-static/test_erf.output
201 
libs/math/test/test_inverse_gamma_distribution.test/gcc-4.8.2/debug/link-static/test_inverse_gamma_distribution.output
201 
libs/math/test/complex_test.test/gcc-4.8.2/debug/link-static/complex_test.output
201 
libs/math/test/test_ibeta_inv_real_concept2.test/gcc-4.8.2/debug/link-static/test_ibeta_inv_real_concept2.output
201 
libs/math/test/powm1_sqrtp1m1_test.test/gcc-4.8.2/debug/link-static/powm1_sqrtp1m1_test.output
201 
libs/math/test/quaternion_test.test/gcc-4.8.2/debug/link-static/quaternion_test.output
201 
libs/math/test/test_binomial_real_concept2.test/gcc-4.8.2/debug/link-static/test_binomial_real_concept2.output
201 
libs/math/test/test_poisson_real_concept.test/gcc-4.8.2/debug/link-static/test_poisson_real_concept.output
201 
libs/math/test/test_inverse_chi_squared_distribution.test/gcc-4.8.2/debug/link-static/test_inverse_chi_squared_distribution.o

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-19 Thread Tony Reix

There are errors specific to Fedora PPC64/BE vs Ubuntu PPC64/LE, and
vice-versa.

Errors specific to Fedora PPC64/BE (none of these errors appears in Ubuntu 
AMD64):
*  1 libs/locale/test/test_boundary.test/gcc-4.8.2/debug/test_boundary.output
*  1 
libs/spirit/test/karma_binary1-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary1-p3.output
*  1 
libs/spirit/test/karma_binary2-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary2-p3.output
*  1 
libs/spirit/test/karma_binary3-p3.test/gcc-4.8.2/debug/phoenix_v3-on/karma_binary3-p3.output
*  1 
libs/spirit/test/qi_binary-p3.test/gcc-4.8.2/debug/phoenix_v3-on/qi_binary-p3.output
*201 
libs/math/test/complex_test.test/gcc-4.8.2/debug/link-static/complex_test.output
*201 
libs/math/test/octonion_test.test/gcc-4.8.2/debug/link-static/octonion_test.output
*201 
libs/math/test/test_long_double_support.test/gcc-4.8.2/debug/link-static/test_long_double_support.output

Errors specific to Ubuntu PPC64/LE  (none of these errors appears in Ubuntu 
AMD64):
*  1   
libs/multiprecision/test/test_arithmetic_ab_1.test/gcc-4.8/debug/test_arithmetic_ab_1.output
*  1   
libs/multiprecision/test/test_arithmetic_backend_concept.test/gcc-4.8/debug/test_arithmetic_backend_concept.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_dec_float_2.test/gcc-4.8/debug/test_arithmetic_cpp_dec_float_2.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_dec_float_3.test/gcc-4.8/debug/test_arithmetic_cpp_dec_float_3.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_10.test/gcc-4.8/debug/test_arithmetic_cpp_int_10.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_11.test/gcc-4.8/debug/test_arithmetic_cpp_int_11.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_12.test/gcc-4.8/debug/test_arithmetic_cpp_int_12.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_13.test/gcc-4.8/debug/test_arithmetic_cpp_int_13.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_16.test/gcc-4.8/debug/test_arithmetic_cpp_int_16.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_1.test/gcc-4.8/debug/test_arithmetic_cpp_int_1.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_2.test/gcc-4.8/debug/test_arithmetic_cpp_int_2.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_4.test/gcc-4.8/debug/test_arithmetic_cpp_int_4.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_5.test/gcc-4.8/debug/test_arithmetic_cpp_int_5.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_7.test/gcc-4.8/debug/test_arithmetic_cpp_int_7.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_8.test/gcc-4.8/debug/test_arithmetic_cpp_int_8.output
*  1   
libs/multiprecision/test/test_arithmetic_cpp_int_9.test/gcc-4.8/debug/test_arithmetic_cpp_int_9.output
*  1   
libs/multiprecision/test/test_arithmetic_dbg_adptr2.test/gcc-4.8/debug/test_arithmetic_dbg_adptr2.output
*  1   
libs/multiprecision/test/test_arithmetic_logged_2.test/gcc-4.8/debug/test_arithmetic_logged_2.output
*139   libs/locale/test/test_boundary.test/gcc-4.8/debug/test_boundary.output
*201   
libs/conversion/test/lexical_cast_inf_nan_test.test/gcc-4.8/debug/link-static/lexical_cast_inf_nan_test.output
*201   libs/geometry/test/algorithms/area.test/gcc-4.8/debug/area.output
*201   libs/geometry/test/algorithms/centroid.test/gcc-4.8/debug/centroid.output
*201   
libs/geometry/test/algorithms/difference.test/gcc-4.8/debug/difference.output
*201   libs/geometry/test/algorithms/expand.test/gcc-4.8/debug/expand.output
*201   
libs/geometry/test/algorithms/intersection.test/gcc-4.8/debug/intersection.output
*201   
libs/geometry/test/algorithms/overlay/ccw_traverse.test/gcc-4.8/debug/ccw_traverse.output
*201   
libs/geometry/test/algorithms/overlay/get_turns.test/gcc-4.8/debug/get_turns.output
*201   
libs/geometry/test/algorithms/overlay/self_intersection_points.test/gcc-4.8/debug/self_intersection_points.output
*201   
libs/geometry/test/algorithms/overlay/traverse.test/gcc-4.8/debug/traverse.output
*201   libs/geometry/test/algorithms/union.test/gcc-4.8/debug/union.output
*201   libs/geometry/test/algorithms/within.test/gcc-4.8/debug/within.output
*201   
libs/geometry/test/multi/algorithms/multi_difference.test/gcc-4.8/debug/multi_difference.output
*201   
libs/geometry/test/multi/algorithms/multi_intersection.test/gcc-4.8/debug/multi_intersection.output
*201   
libs/geometry/test/multi/algorithms/multi_union.test/gcc-4.8/debug/multi_union.output
*201   
libs/math/test/test_bessel_i.test/gcc-4.8/debug/link-static/test_bessel_i.output
*201   
libs/math/test/test_bessel_k.test/gcc-4.8/debug/link-static/test_bessel_k.output
*201   
libs/math/test/test_ellint_2.test/gcc-4.8/debug/link-static/test_ellint_2.output
*201   
libs/math/test/test_ellint_3.test/gcc-4.8/debug/link-static/test_ellint_3.output

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-19 Thread Tony Reix

There are few PPC assembler files in Boost (v1.55) :
./libs/context/src/asm/jump_ppc64_sysv_elf_gas.S
./libs/context/src/asm/jump_ppc32_sysv_elf_gas.S
./libs/context/src/asm/make_ppc64_sysv_elf_gas.S
./libs/context/src/asm/make_ppc32_sysv_elf_gas.S

And I've not found any PPC assembler code included in C++ files. Only
Intel assembler optimizations.

That means to says that assembler code in Boost should not be the root
cause of the issues I've found. Moreover, though there are more issues
on Ubuntu PPC64/LE than on Fedora PPC64/BE, there are issues on
PPC64/BE, which has a stable ABI compared to the recently changed ABI on
PPC64/LE .

Understanding and fixing errors common to both PPC64 BE and LE would
help, as a first attempt.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1282140] [NEW] core on 64bit arch in spirit ... lex_lexertl2-p3 test

2014-02-19 Thread Tony Reix

Public bug reported:

Test :
 
./boost1.55-1.55.0/bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3

SegFaults on 64 bits machines (AMD64 and PPC64).


The issue is that :
   CharT curr_char_ = (std::numeric_limits::min)();
returns  
   0x8000
when CharT is wchar_t .


And curr_char (0x8000)  is then used in:
   ptr_[curr_char_]
which cores.


I think that some macros have been defined in /usr/include/c++/4.8.2/limits  
that work fine for "char" type but not for "wchar_t" type in 64bits world.

 min() _GLIBCXX_USE_NOEXCEPT { return __glibcxx_min(char); } returns  0 .
 min() _GLIBCXX_USE_NOEXCEPT { return __glibcxx_min(wchar_t); }returns  
0x8000 .

So, that could be an issue in libC++ . Or not. I'm not an expert and I
need someone to look at this.

See PPC64/BE part for more details (values of registers and names of
files).


=

On AMD64 (Ubuntu 14.04):

gdb
./boost1.55-1.55.0/bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3

(gdb) break generator.hpp:564
Breakpoint 1 at 0x424945: generator.hpp:564. (2 locations)

(gdb) run
Starting program: 
/home/ubuntu/BOOST/boost1.55/boost1.55-1.55.0/bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3
 

Breakpoint 1, boost::lexer::basic_generator >::fill_lookup (token_=..., lookup_=0x690030, 
index_=4) at ../boost/spirit/home/support/detail/lexer/generator.hpp:564
564 ../boost/spirit/home/support/detail/lexer/generator.hpp: No such file 
or directory.
(gdb) c
Continuing.

Breakpoint 1, boost::lexer::basic_generator >::fill_lookup (token_=..., 
lookup_=0x6901b0, index_=4)
at ../boost/spirit/home/support/detail/lexer/generator.hpp:564
564 in ../boost/spirit/home/support/detail/lexer/generator.hpp
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x0042907b in boost::lexer::basic_generator >::fill_lookup (token_=..., 
lookup_=0x6901b0, index_=4)
at ../boost/spirit/home/support/detail/lexer/generator.hpp:571
571 in ../boost/spirit/home/support/detail/lexer/generator.hpp


(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program:
/home/ubuntu/BOOST/boost1.55/boost1.55-1.55.0/bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3

Breakpoint 1, boost::lexer::basic_generator >::fill_lookup (token_=..., lookup_=0x690030, 
index_=4) at ../boost/spirit/home/support/detail/lexer/generator.hpp:564
564 in ../boost/spirit/home/support/detail/lexer/generator.hpp
(gdb) c
Continuing.

Breakpoint 1, boost::lexer::basic_generator >::fill_lookup (token_=..., 
lookup_=0x6901b0, index_=4)
at ../boost/spirit/home/support/detail/lexer/generator.hpp:564
564 in ../boost/spirit/home/support/detail/lexer/generator.hpp
(gdb) p curr_char_
$1 = 0 L'\000'
(gdb) si
std::numeric_limits::min () at /usr/include/c++/4.8/limits:655
655   min() _GLIBCXX_USE_NOEXCEPT { return __glibcxx_min (wchar_t); }
(gdb) si
0x00404b47  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
(gdb) si
655   min() _GLIBCXX_USE_NOEXCEPT { return __glibcxx_min (wchar_t); }
(gdb) si
0x00404b4f  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
(gdb) display/i $pc
1: x/i $pc
=> 0x404b4f ::min()+9>:shl$0x3,%eax
(gdb) si
0x00404b52  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b52 ::min()+12>:   sub$0x2,%eax
(gdb) si
0x00404b55  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b55 ::min()+15>:   mov$0x1,%edx
(gdb) si
0x00404b5a  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b5a ::min()+20>:   mov%eax,%ecx
(gdb) si
0x00404b5c  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b5c ::min()+22>:   shl%cl,%edx
(gdb) si
0x00404b5e  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b5e ::min()+24>:   mov%edx,%eax
(gdb) si
0x00404b60  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b60 ::min()+26>:   sub$0x1,%eax
(gdb) si
0x00404b63  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b63 ::min()+29>:   lea
(%rax,%rax,1),%edx
(gdb) si
0x00404b66  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x/i $pc
=> 0x404b66 ::min()+32>:   mov$0xfffe,%eax
(gdb) si
0x00404b6b  655   min() _GLIBCXX_USE_NOEXCEPT { return 
__glibcxx_min (wchar_t); }
1: x

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-20 Thread Tony Reix

This is described in comment #12 :
   https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/comments/12
(However, I've just found that core (error 139) on PPC64/LE also appears on 
AMD64: my mistake).

Boost 1.55 on PPC64 shows more and different issues on LE than on BE. However, 
same faulty code may generate different errors according to the testing 
environment.
I'm still investigating. make/jump_ppc32_sysv_elf_gas.S seems to be the root 
cause for all PPC64 BE & LE cores. Trying to figure out what is the root cause 
in this assembler code. Maybe some PPC64 fixes were produced but are not 
available on versions 1.54 and 1.55 of Boost. I'll look at most recent versions 
of Boost.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-20 Thread Tony Reix

Revision 86799 of :
./libs/context/src/asm/jump_ppc64_sysv_elf_gas.S
./libs/context/src/asm/make_ppc64_sysv_elf_gas.S
is exactly identical to the version delivered with Boost v1.55 .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] [NEW] OptionParser on PPC64LE does not split args correctly

2014-10-08 Thread Tony Reix

Public bug reported:

The issue appears on PPC64 LE.
It is OK on (Ubuntu) x86_64.
Version of Python is 2.7.6 on both systems.
The issue is demonstrated while running AVRO Python tests (in lang/py : ant 
test).


- On Ubuntu / PPC64 LE :

$ pwd
/lang/py
$ export PYTHONPATH=./build/src
$ /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/../scripts/avro 
cat /tmp/REIX --fields 'first, last'
{"first": "daffy"}
{"first": "bugs"}
{"first": "tweety"}
{"first": "road"}
{"first": "wile"}
{"first": "pepe"}
{"first": "foghorn"}
Usage: avro cat|write [options] FILE [FILE...]

avro: error: Can't open last - [Errno 2] No such file or directory: 'last'
$ echo $?
2

The issue is that 'first, last' is not parsed correctly. The white space
between "," and "last" is parsed in a way that makes "last" been
interpreted as a "FILE" instead of an option.


Without the white space, that works fine:

$ /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/../scripts/avro 
cat /tmp/REIX --fields 'first,last'
{"last": "duck", "first": "daffy"}
{"last": "bunny", "first": "bugs"}
{"last": "", "first": "tweety"}
{"last": "runner", "first": "road"}
{"last": "e", "first": "wile"}
{"last": "le pew", "first": "pepe"}
{"last": "leghorn", "first": "foghorn"}
$ echo $?
0


- On Ubuntu / x86_64, both 'first, last' and 'first,last' are OK:

$ pwd
/lang/py
$ export PYTHONPATH=./build/src
$ build/test/../scripts/avro cat /tmp/REIX --fields 'first, last'
{"last": "duck", "first": "daffy"}
{"last": "bunny", "first": "bugs"}
{"last": "", "first": "tweety"}
{"last": "runner", "first": "road"}
{"last": "e", "first": "wile"}
{"last": "le pew", "first": "pepe"}
{"last": "leghorn", "first": "foghorn"}
$ echo $?
0


Source code of: 
/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/../scripts/avro  
is:

def main(argv=None):
import sys
from optparse import OptionParser, OptionGroup

argv = argv or sys.argv

parser = OptionParser(description="Display/write for Avro files",
  version="1.7.4",
  usage="usage: %prog cat|write [options] FILE [FILE...]")


So, OptionParser() does not work on PPC64 like it does on x86_64.

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-08 Thread Tony Reix

In Avro, the issue appears as:

  [py-test] ERROR: test_fields (test_script.TestCat)
  [py-test] 
--
  [py-test] Traceback (most recent call last):
  [py-test]   File 
"/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/test_script.py", 
line 169, in test_fields
  [py-test] out = self._run('--fields', 'first, last')
  [py-test]   File 
"/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/test_script.py", 
line 109, in _run
  [py-test] out = check_output([SCRIPT, "cat", self.avro_file] + list(args))
  [py-test]   File "/usr/lib/python2.7/subprocess.py", line 573, in check_output
  [py-test] raise CalledProcessError(retcode, cmd, output=output)
  [py-test] CalledProcessError: Command 
'['/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/../scripts/avro',
 'cat', '/tmp/tmp3Oiy6H', '--fields', 'first, last']' returned non-zero exit 
status 2


If the string 'first, last' is replaced by 'first,last' (no space), another 
issue appears (that does not appear on x86_64), with the string '' :

  [py-test] ERROR: test_fields (test_script.TestCat)
  [py-test] Traceback (most recent call last):
  [py-test]
  [py-test]   File 
"/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/test_script.py", 
line 173, in test_fields
  [py-test] Schema: ["string", "null", "long"]
  [py-test] out = self._run('--fields', '')
  [py-test] Datum: None
  [py-test]   File 
"/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/test_script.py", 
line 109, in _run
  [py-test] Codec: deflate
  [py-test] out = check_output([SCRIPT, "cat", self.avro_file] + list(args))
  [py-test] Round Trip Data: [None, None, None, None, None, None, None, None, 
None, None]
  [py-test]   File "/usr/lib/python2.7/subprocess.py", line 573, in check_output
  [py-test] Round Trip Data Length: 10
  [py-test] raise CalledProcessError(retcode, cmd, output=output)
  [py-test] Correct Round Trip: True
  [py-test]
  [py-test] CalledProcessError: Command 
'['/home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/test/../scripts/avro',
 'cat', '/tmp/tmpJJp2gX', '--fields', '']' returned non-zero exit status 2


The issue in Python is triggered by this Avro test file:
lang/py/build/test/test_script.py

class TestCat(unittest.TestCase):
.
 def test_fields(self):
 ...
# Field selection (with comma and space)
out = self._run('--fields', 'first, last')
assert json.loads(out[0]) == {'first': 'daffy', 'last': 'duck'}

# Empty fields should get all
out = self._run('--fields', '')


So, there are 2 issues with OptionParser():
 - 'first, last'
 - ''  (empty field)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

/tmp/REIX file for testing.

** Attachment added: "File for testing. Produced on PPC64LE by Avro test code"
   
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+attachment/4229394/+files/REIX.PPC64LE

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

Hi Breno,

I have changed the source code of the Avro Python tests in order to save
the temporary file used by the test. I saved it in a file I named
/tmp/REIX . This file contains non-asci data. I gonna attach it to this
bug. Also, I think this file depends on the machine architecture.

About the "avro" command you used, maybe you are not using the correct one. I 
do not see any scripts-2.7 directory .
Maybe you have to try:
  cd lang/py/build/scripts
  ./avro cat /tmp/REIX --fields 'first, last'

Tony

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

Hi Matthias,
We have checked, and there is no 14.10 version yet for PPC64LE.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1282140] Re: core on 64bit arch in spirit ... lex_lexertl2-p3 test

2014-03-06 Thread Tony Reix

Hu OK. I'll dig that later, and open a defect in Boost world.
Thanks !
Tony

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282140

Title:
  core on 64bit arch in spirit ... lex_lexertl2-p3 test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.55/+bug/1282140/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1288884] [NEW] Boost: patch for context/coroutine libraries for LoP PPC64

2014-03-06 Thread Tony Reix

Public bug reported:

Hello

I'm preparing a patch for Boost v1.55 for context & coroutine libraries for 
Linux on Power PPC64 LITTLE Endian.
The code is the same (using #if) for Boost v1.55 for context & coroutine 
libraries for Linux on Power PPC64 BIG Endian.

Files :
libs/context/src/asm/jump_ppc64_sysv_elf_gas.S
libs/context/src/asm/make_ppc64_sysv_elf_gas.S

The current files of Boost v1.55 delivered by Ubuntu 14.04 for Linux on
Power PPC64 LE (& BE) generate a segfault for the tests of the 2
libraries context & coroutine.

The current code of context & coroutine libraries in "develop" version
of Boost has changed. API has changed. Thus, the patches for Boost v1.55
and for future version of Boost will be different. I'll deliver them in
parallel (for Ubuntu and for Boost project).

I have built files that make the Boost v1.55 context and coroutine tests work 
fine on Linux on Power PPC64 LE & BE.
However, I have no way to test on other different PPC environment.

The lines that control compiling these .S files are (in file
libs/context/build/Jamfile.v2) :

# POWERPC_64
alias asm_context_sources
   : asm/make_ppc64_sysv_elf_gas.S
 asm/jump_ppc64_sysv_elf_gas.S
   : 64
 power
 elf
 gcc
   ;

I do not master Jam, and I don't know if these lines are used by other PPC64 
environment.
So, if you use my changes for modifying the Boost source code used by Ubuntu 
14.04 only for IBM PowerPC64 machines with Linux BE or LE, that will work fine.
If the way you manage source code is centralized for different targets 
(including other PPC64 environments I'm not aware of), that should not work, 
and files should be named in a different way, and the Jamfile.v2 will have to 
be changed too .

I need some advice.

Regards,
Tony

** Affects: boost1.55 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "First proposal"
   
https://bugs.launchpad.net/bugs/124/+attachment/4010110/+files/ppc64_sysv_elf_gas.S.tar

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/124

Title:
  Boost: patch for context/coroutine libraries for LoP PPC64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.55/+bug/124/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1294588] [NEW] glibc: some long double math routines for PPC64 are wrong: patches

2014-03-19 Thread Tony Reix

Public bug reported:

Within glibc (2.19 on Ubuntu, but also on 2.17), some "long double"
routines for PPC64 are wrong: both .c and .S files exist, and .S files
are taken first though they are old and wrong. The bugs appear for some
cases (for ceill(), second double is wrong). The fix is easy: remove the
wrong .S files so that the correct .c files are used for building
libm.so  (/lib/powerpc64le-linux-gnu/libm-2.19.so).

The impacted routines are: ceill, roundl, etc.
The patches have already been integrated into glibc at sourceware.org :

Assuming GLIBC 2.19, you need these patches:
https://sourceware.org/git/?p=glibc.git;a=commit;h=374f7f61214967bb4e2257695acc2a77f369
https://sourceware.org/git/?p=glibc.git;a=commit;h=98fb27a373f37554232e0060eef1a5bb00a07eb0
https://sourceware.org/git/?p=glibc.git;a=commit;h=c7de50250367167d8c9f35594b264f6a0af8dd0c

Regards,

Tony

** Affects: pcre3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294588

Title:
  glibc: some long double math routines for PPC64 are wrong: patches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1294588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1294588] Re: glibc: some long double math routines for PPC64 are wrong: patches

2014-03-19 Thread Tony Reix

** Package changed: pcre3 (Ubuntu) => eglibc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1294588

Title:
  glibc: some long double math routines for PPC64 are wrong: patches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1294588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1270862] [NEW] libpcre3 1:8.31-2ubuntu2 : not ready for --enable-jit option

2014-01-20 Thread Tony Reix

Public bug reported:

Version 8.31 of libpcre3 (pcre3 sources) is not ready for --enable-jit
option on Linux/PPC64 LE. It even does not compile.

Version 8.34 of libpcre3 does include code for Linux on PPC64-LE. However, this 
code still fails for JIT. It is being fixed now.
Staty tune with:  http://bugs.exim.org/show_bug.cgi?id=1430 .

The current version 8.31 of libpcre3 on Ybuntu PPC64/LE should be
replaced by the version (8.35 ?) that fixes the JIT issues on PPC64/LE
(it is OK on PPC64/BE).


/home/tony/PCRE/pcre3-8.31:

In file included from sljit/sljitNativePPC_common.c:417:0,
 from sljit/sljitLir.c:1251,
 from pcre_jit_compile.c:62:
sljit/sljitNativePPC_64.c: In function 'sljit_set_function_context':
sljit/sljitNativePPC_64.c:425:9: error: dereferencing pointer to incomplete type
  context->addr = addr ? addr : ptrs[0];
 ^
sljit/sljitNativePPC_64.c:426:9: error: dereferencing pointer to incomplete type
  context->r2 = ptrs[1];
 ^
sljit/sljitNativePPC_64.c:427:9: error: dereferencing pointer to incomplete type
  context->r11 = ptrs[2];


pcre-8.34:

make  check-TESTS
make[2]: Entering directory `/home/tony/PCRE/pcre-8.XX/trunk'
make[3]: Entering directory `/home/tony/PCRE/pcre-8.XX/trunk'
./test-driver: line 107: 32524 Illegal instruction (core dumped) "$@" > 
$log_file 2>&1
FAIL: pcre_jit_test


$ lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04


$ lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04
tony@tony1:~/PCRE/pcre3-8.31$ apt-cache policy libpcre3
libpcre3:
  Installed: 1:8.31-2ubuntu2
  Candidate: 1:8.31-2ubuntu2
  Version table:
 *** 1:8.31-2ubuntu2 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main ppc64el Packages
100 /var/lib/dpkg/status

** Affects: pcre3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270862

Title:
  libpcre3 1:8.31-2ubuntu2 : not ready for  --enable-jit option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1270862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1270862] Re: libpcre3 1:8.31-2ubuntu2 : not ready for --enable-jit option

2014-02-04 Thread Tony Reix

Here is the trace when building PCRE 8.31 from Ubuntu sources:

sudo dpkg-buildpackage

...

CC_FOR_BUILD=cc CPPFLAGS="-D_FORTIFY_SOURCE=2" CFLAGS="-Wall -g -O2 
-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security" 
LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro" \
./configure \
--host=powerpc64le-linux-gnu --build=powerpc64le-linux-gnu \
--prefix=/usr --mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info \
--libdir=\${prefix}/lib/powerpc64le-linux-gnu \
--enable-utf8 --enable-unicode-properties \
--disable-silent-rules

No JIT,  and no 16bit library.

pcre-8.31 configuration summary:

Install prefix .. : /usr
C preprocessor .. : powerpc64le-linux-gnu-gcc -E
C compiler .. : powerpc64le-linux-gnu-gcc
C++ preprocessor  : powerpc64le-linux-gnu-g++ -E
C++ compiler  : powerpc64le-linux-gnu-g++
Linker .. : /usr/bin/ld
C preprocessor flags  : -D_FORTIFY_SOURCE=2
C compiler flags  : -Wall -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security
C++ compiler flags .. : -O2
Linker flags  : -Wl,-Bsymbolic-functions -Wl,-z,relro
Extra libraries . :

Build 8 bit pcre library  : yes
Build 16 bit pcre library ... : no
Build C++ library ... : yes
Enable JIT compiling support  : no
Enable UTF-8/16 support . : yes
Unicode properties .. : yes
Newline char/sequence ... : lf
\R matches only ANYCRLF . : no
EBCDIC coding ... : no
Rebuild char tables . : no
Use stack recursion . : yes
POSIX mem threshold . : 10
Internal link size .. : 2
Match limit . : 1000
Match limit recursion ... : MATCH_LIMIT
Build shared libs ... : yes
Build static libs ... : yes
Use JIT in pcregrep . : no
Buffer size for pcregrep  : 20480
Link pcregrep with libz . : no
Link pcregrep with libbz2 ... : no
Link pcretest with libedit .. : no
Link pcretest with libreadline .. : no

PASS: pcrecpp_unittest
PASS: pcre_scanner_unittest
PASS: pcre_stringpiece_unittest
PASS: RunTest
PASS: RunGrepTest


In order to check that all main PCRE features run fine on Ubuntu/PPC/LE, at 
least the following options should be added to the ./configure line: 
--enable-shared=no --enable-pcre16 --enable-pcre32 --enable-unicode-properties 
--enable-jit

Using --enable-jit with this 8.31 version will not work; too old for
PPC. Use fresher version, like 8.34 . However, work is still being done
for making JIT test OK on PCRE 8.34 on Ubuntu/PPC/LE (ABI issue).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270862

Title:
  libpcre3 1:8.31-2ubuntu2 : not ready for  --enable-jit option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1270862/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] [NEW] Many tests of Boost v1.54 fail

2014-02-04 Thread Tony Reix

Public bug reported:

I'm now testing Boost v1.54 from Ubuntu sources.

I've done:

sudo apt-get update
sudo apt-get install libboost-dev
sudo apt-get install libboost-all-dev
sudo apt-get install dpkg-dev
sudo apt-get build-dep boost1.54
 apt-get source boost1.54
sudo apt-get build-dep boost1.54
cd boost1.54-1.54.0
sudo dpkg-buildpackage
cd status
../b2 2>&1 | tee ../../b2.TestAll.1.log


and I've got the following errors:

boost1.54-1.54.0/bin.v2/libs/tr1/test/run_random.test/gcc-4.8/debug/run_random.output
 - 201
boost1.54-1.54.0/bin.v2/libs/tr1/test/std_run_random.test/gcc-4.8/debug/std_run_random.output
 - 201
boost1.54-1.54.0/bin.v2/libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output
 - 139
boost1.54-1.54.0/bin.v2/libs/conversion/test/lexical_cast_inf_nan_test.test/gcc-4.8/debug/link-static/lexical_cast_inf_nan_test.output
 - 201
boost1.54-1.54.0/bin.v2/libs/conversion/test/lexical_cast_loopback_test.test/gcc-4.8/debug/link-static/lexical_cast_loopback_test.output
 - 201
boost1.54-1.54.0/bin.v2/libs/conversion/test/lexical_cast_float_types_test.test/gcc-4.8/debug/link-static/lexical_cast_float_types_test.output
 - 201
boost1.54-1.54.0/bin.v2/libs/filesystem/test/operations_test_static.test/gcc-4.8/debug/link-static/operations_test_static.output
 - 139
boost1.54-1.54.0/bin.v2/libs/coroutine/test/test_coroutine.test/gcc-4.8/debug/link-static/test_coroutine.output
 - 139
Looping : 
../bin.v2/libs/flyweight/test/test_intermod_holder.test/gcc-4.8/debug/threading-multi/test_intermod_holder

Tests were blocked due to  "test_intermod_holder" looping infinitely. I
have to run the tests after this blocking test.


Results were compared to Boost results on page: 
http://beta.boost.org/development/tests/master/developer/summary.html .
Though some tests do fail on x86 platform, many tests should succeed and, for 
sure, should not core or run in an infinite loop.

So, these errors should be investigated and fixed.
First try to understand a core goes into libs C and C++.

About version 1.55, I also have many failures (test failed, core,
infinite loop, plus bad memory access).

Tony


boost1.54-1.54.0/bin.v2/libs/tr1/test/run_random.test/gcc-4.8/debug/run_random.output
:

Based on Boost DataBase, this test fails everywhere. Not a problem.


boost1.54-1.54.0/bin.v2/libs/tr1/test/std_run_random.test/gcc-4.8/debug/std_run_random.output:

Based on Boost DataBase, this test fails everywhere. Not a problem.


boost1.54-1.54.0/bin.v2/libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output:

Segmentation fault (core dumped)


boost1.54-1.54.0/bin.v2/libs/conversion/test/lexical_cast_inf_nan_test.test/gcc-4.8/debug/link-static/lexical_cast_inf_nan_test.output:

../libs/conversion/test/lexical_cast_inf_nan_test.cpp(73): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-inf") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(74): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-INF") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(82): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-infinity") 
) failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(83): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-INFINITY") 
) failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(91): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-inFINITY") 
) failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(92): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast("-INFINITY") 
) failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(97): error in 
"test_inf_nan_long_double": check is_neg_nan( lexical_cast("-nan") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(98): error in 
"test_inf_nan_long_double": check is_neg_nan( lexical_cast("-NAN") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(106): error in 
"test_inf_nan_long_double": check is_neg_nan( lexical_cast("-nAn") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(107): error in 
"test_inf_nan_long_double": check is_neg_nan( lexical_cast("-NaN") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(117): error in 
"test_inf_nan_long_double": check lexical_cast( 
(boost::math::changesign)(std::numeric_limits::infinity())) == "-inf" 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(123): error in 
"test_inf_nan_long_double": check lexical_cast( 
(boost::math::changesign)(std::numeric_limits::quiet_NaN())) == "-nan" 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(130): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast(L"-inf") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(131): error in 
"test_inf_nan_long_double": check is_neg_inf( lexical_cast(L"-INF") ) 
failed
../libs/conversion/test/lexical_cast_inf_nan_test.cpp(139): error in 
"test

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-04 Thread Tony Reix

I forgot to say that this is on PPC/LE  with alpha2 .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-05 Thread Tony Reix

Here are the traces for one of the cores:

boost1.54-1.54.0/bin.v2/libs/filesystem/test/operations_test_static.test/gcc-4.8/debug/link-static/operations_test_static
Program received signal SIGSEGV, Segmentation fault.

__atomic_add_dispatch (__val=1, __mem=0x0) at 
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/ext/atomicity.h:98
98  
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/ext/atomicity.h:
 No such file or directory.
1: x/i $pc
=> 0x3fffb7ee28ec : lwz 
r10,0(r9)


__atomic_add_dispatch (__val=1, __mem=0x0) at 
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/ext/atomicity.h:98
98  
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/ext/atomicity.h:
 No such file or directory.

(gdb) where
#0  __atomic_add_dispatch (__val=1, __mem=0x0) at 
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/ext/atomicity.h:98
#1  _M_add_reference (this=0x0) at 
/build/buildd/gcc-4.8-4.8.2/build/powerpc64le-linux-gnu/libstdc++-v3/include/bits/locale_classes.h:510
#2  std::locale::locale (this=0x100783d0 
, __other=...) 
at ../../../../../src/libstdc++-v3/src/c++98/locale.cc:80
#3  0x100492a8 in boost::filesystem::path::imbue (loc=...) at 
../libs/filesystem/src/path.cpp:918
#4  0x100491b0 in boost::filesystem::path::codecvt () at 
../libs/filesystem/src/path.cpp:911
#5  0x1004aa3c in boost::filesystem::path::wstring 
(this=0x35c8) at ../boost/filesystem/path.hpp:386
#6  0x1004a540 in boost::filesystem::detail::unique_path (model=..., 
ec=0x0) at ../libs/filesystem/src/unique_path.cpp:113
#7  0x100238c4 in boost::filesystem::unique_path (p=...) at 
../boost/filesystem/operations.hpp:544
#8  0x100200cc in __static_initialization_and_destruction_0 
(__initialize_p=1, __priority=65535) at 
../libs/filesystem/test/operations_test.cpp:118
#9  0x100201fc in _GLOBAL__sub_I__Z8cpp_mainiPPc () at 
../libs/filesystem/test/operations_test.cpp:2034
#10 0x1004d444 in __libc_csu_init ()
#11 0x3fffb7c8e1ec in generic_start_main (main=0x1003173c , argc=, argv=0x3a68, auxvec=0x3b10, 
init=0x1004d3b0 <__libc_csu_init>,
rtld_fini=, stack_end=, fini=) 
at ../csu/libc-start.c:246
#12 0x3fffb7c8e458 in __libc_start_main (argc=, 
argv=, ev=, auxvec=, 
rtld_fini=, stinfo=,
stack_on_entry=) at 
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:93
#13 0x in ?? ()


Breakpoint 1, boost::filesystem::path::imbue (loc=...) at 
../libs/filesystem/src/path.cpp:918
918 std::locale temp(path_locale);

 p loc
$1 = (const std::locale &) @0x3418: {static none = 0, static ctype = 1, 
static numeric = 2, static collate = 4, static time = 8, static monetary = 16, 
static messages = 32, static all = 63,
  _M_impl = 0x100790f0, static _S_classic = 0x3fffb7fae0b8 <(anonymous 
namespace)::c_locale_impl>, static _S_global = 0x3fffb7fae0b8 <(anonymous 
namespace)::c_locale_impl>, static _S_categories =
0x3fffb7f92cb8 <__gnu_cxx::category_names>, static _S_once = 0}

 p path_locale
$2 = {static none = 0, static ctype = 1, static numeric = 2, static collate = 
4, static time = 8, static monetary = 16, static messages = 32, static all = 
63, _M_impl = 0x0,
  static _S_classic = 0x3fffb7fae0b8 <(anonymous namespace)::c_locale_impl>, 
static _S_global = 0x3fffb7fae0b8 <(anonymous namespace)::c_locale_impl>,
  static _S_categories = 0x3fffb7f92cb8 <__gnu_cxx::category_names>, static 
_S_once = 0}


It looks like something wrong happened here:

  std::locale::locale (this=0x100783d0 
, __other=...)
  at ../../../../../src/libstdc++-v3/src/c++98/locale.cc:80

in the libstdc++ library, since correct address was changed to 0x0
address in __atomic_add_dispatch .


BOOST :
libs/filesystem/src/path.cpp
  std::locale path::imbue(const std::locale& loc)
  {
std::locale temp(path_locale);
path_locale = loc;
codecvt_facet_ptr =
  &std::use_facet 
>(path_locale);
return temp;
  }


/usr/include/c++/4.8/ext/atomicity.h

  static inline void
  __attribute__ ((__unused__))
  __atomic_add_dispatch(_Atomic_word* __mem, int __val)
  {
#ifdef __GTHREADS
if (__gthread_active_p())
  __atomic_add(__mem, __val);
else
  __atomic_add_single(__mem, __val);
#else
__atomic_add_single(__mem, __val);
#endif
  }


It looks like some C++ object initialization went bad, for  std::locale::locale 
.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-06 Thread Tony Reix

After debugging "some" more, it looks like the issue is in:

BOOST : libs/filesystem/src/path.cpp

  std::locale path::imbue(const std::locale& loc)
  {
std::locale temp(path_locale);<<<  line 918
path_locale = loc;
codecvt_facet_ptr =
  &std::use_facet 
>(path_locale);
return temp;
  }

At line 918, C++ try to do some initialization. This seems to imply to use 
field _M_impl of path_locale, which is 0x0.
It seems that no initialization of path_locale is done and thus _M_impl stay 
0x0.

p path_locale
$23 = {static none = 0, static ctype = 1, static numeric = 2, static collate = 
4, static time = 8, static monetary = 16, static messages = 32, static all = 
63, _M_impl = 0x0, 
  static _S_classic = 0x3fffb7fae0b8 <(anonymous namespace)::c_locale_impl>, 
static _S_global = 0x3fffb7fae0b8 <(anonymous namespace)::c_locale_impl>, 
static _S_categories = 
0x3fffb7f92cb8 <__gnu_cxx::category_names>, static _S_once = 0}


So, the question is: why path_locale has not been initialized ? and why this 
happens in PPC/LE and not elsewhere ?

Since, at line 868, we have:

 std::locale path_locale;  // initialized by path::codecvt() below
  const std::codecvt* codecvt_facet_ptr;  // 
ditto

which does not seems to do any initialization (gdb don't stop there).
however, the comment says that path_locale is initialiazed by line
below, where gdb does not stop.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-11 Thread Tony Reix

On my PC, running oneiric, version 11.10,  on Xeon, with gcc 4.6.1, I also see 
errors when testing Boost v1.55.
EXIT STATUS are:
  1 : 11  (False results)
134 :1   (Exception, aborted)
139 :2   (Seg Fault)
200 : 10   (memory access violation)
201 :   8   (error detected)

I have to find a x86 machine I can install with a fresh Ubuntu. No time
for doing that for now, but I'll do.

When comparing what I get on PPC/LE and my PC, about most important errors (seg 
fault, memory acces, exception aborted), I have:
- Errors on both environments:
   ES 134:
  
../bin.v2/libs/spirit/test/qi_match_manip1-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_match_manip1-p3.output
   ES 139:
  
../bin.v2/libs/spirit/test/lex_lexertl2-p3.test/gcc-*/debug/phoenix_v3-on/lex_lexertl2-p3.output
 
../bin.v2/libs/filesystem/test/operations_test_static.test/gcc-*/debug/link-static/operations_test_static.output
   ES 200:
 
../bin.v2/libs/heap/test/binomial_heap_test.test/gcc-*/debug/threading-multi/binomial_heap_test.output
 
../bin.v2/libs/heap/test/pairing_heap_tests.test/gcc-*/debug/threading-multi/pairing_heap_tests.output
 
../bin.v2/libs/heap/test/skew_heap_test.test/gcc-*/debug/threading-multi/skew_heap_test.output"
 
../bin.v2/libs/heap/test/mutable_heap_test.test/gcc-*1/debug/threading-multi/mutable_heap_test.output"
 
../bin.v2/libs/heap/test/fibonacci_heap_test.test/gcc-*1/debug/threading-multi/fibonacci_heap_test.output"
 
../bin.v2/libs/heap/test/priority_queue_test.test/gcc-*/debug/threading-multi/priority_queue_test.output"

- Errors only on PPC/LE :
   ES 134: NONE
   ES 139:
  
../bin.v2/libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output
  
../bin.v2/libs/coroutine/test/test_coroutine.test/gcc-4.8/debug/link-static/test_coroutine.output
  
../bin.v2/libs/locale/test/test_boundary.test/gcc-4.8/debug/test_boundary.output
   ES 200:

../bin.v2/libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output

../bin.v2/libs/test/test/prg_exec_fail2.test/gcc-4.8/debug/prg_exec_fail2.output

- Errors only on x86_64:
   ES 200:
 
../bin.v2/libs/heap/test/d_ary_heap_test.test/gcc-4.6.1/debug/threading-multi/d_ary_heap_test.output"


So, there are cores and memory access violations that are specific to PPC/LE.
And there are cores and memory access violations that are common to both 
environments, though they use different versions of GCC.

I am now building/testing on PPC/BE in order to compare. It uses same
version of GCC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-12 Thread Tony Reix

I now have a Ubuntu-amd64 (x86_64) environment, where I am
building/testing Boost 1.55 and then 1.54.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-14 Thread Tony Reix

Results for Boost 1.55 on Ubuntu 14.04 on amd64 with gcc 4.8.2 (Ubuntu
4.8.2-15ubuntu3) :

(Linux version 3.13.0-8-generic (buildd@lamiak) (gcc version 4.8.2
(Ubuntu/Linaro 4.8.2-14ubuntu4) ) #27-Ubuntu SMP Fri Feb 7 02:01:37 UTC
2014)

4401 tests

Number of Memory Access Violation:  7
libs/heap/test/binomial_heap_test.test/gcc-4.8/debug/threading-multi/binomial_heap_test.output
libs/heap/test/priority_queue_test.test/gcc-4.8/debug/threading-multi/priority_queue_test.output
libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output
libs/heap/test/fibonacci_heap_test.test/gcc-4.8/debug/threading-multi/fibonacci_heap_test.output
libs/heap/test/mutable_heap_test.test/gcc-4.8/debug/threading-multi/mutable_heap_test.output
libs/heap/test/skew_heap_test.test/gcc-4.8/debug/threading-multi/skew_heap_test.output
libs/heap/test/pairing_heap_tests.test/gcc-4.8/debug/threading-multi/pairing_heap_tests.output

Number of sub-tests failed:  18

Number of cores: 2
  
./boost1.55-1.55.0/bin.v2/libs/log/test/core.test/gcc-4.8/debug/threading-multi/core
  ./boost1.55-1.55.0/bin.v2/libs/phoenix/test/core.test/gcc-4.8/debug/core


Exit  | Number
Status |  of results

  0   4373
  1 9
134  1
139  3
20010
201  4

Tot 4401


Details of errors:
139   
libs/filesystem/test/operations_test_static.test/gcc-4.8/debug/link-static/operations_test_static.output
201   
libs/ptr_container/test/serialization.test/gcc-4.8/debug/serialization.output
  1   
libs/wave/test/build/testwave.test/gcc-4.8/debug/link-static/threading-multi/testwave.output
  1   
libs/spirit/repository/test/qi_repo_keywords.test/gcc-4.8/debug/qi_repo_keywords.output
  1   
libs/spirit/test/qi_int1-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_int1-p3.output
139   
libs/spirit/test/lex_lexertl2-p3.test/gcc-4.8/debug/phoenix_v3-on/lex_lexertl2-p3.output
134   
libs/spirit/test/qi_match_manip1-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_match_manip1-p3.output
  1   
libs/spirit/test/karma_real1-p3.test/gcc-4.8/debug/phoenix_v3-on/karma_real1-p3.output
  1   
libs/spirit/test/qi_regression_stream_eof-p3.test/gcc-4.8/debug/phoenix_v3-on/qi_regression_stream_eof-p3.output
  1   
libs/spirit/test/karma_real2-p3.test/gcc-4.8/debug/phoenix_v3-on/karma_real2-p3.output
  1   
libs/spirit/test/karma_alternative1-p3.test/gcc-4.8/debug/phoenix_v3-on/karma_alternative1-p3.output
201   libs/test/test/minimal_test.test/gcc-4.8/debug/minimal_test.output
200   libs/test/test/prg_exec_fail2.test/gcc-4.8/debug/prg_exec_fail2.output
200   libs/test/test/prg_exec_fail1.test/gcc-4.8/debug/prg_exec_fail1.output
  1   libs/test/test/prg_exec_fail4.test/gcc-4.8/debug/prg_exec_fail4.output
200   libs/test/test/prg_exec_fail3.test/gcc-4.8/debug/prg_exec_fail3.output
201   libs/tr1/test/run_random.test/gcc-4.8/debug/run_random.output
201   libs/tr1/test/std_run_random.test/gcc-4.8/debug/std_run_random.output
139   libs/locale/test/test_boundary.test/gcc-4.8/debug/test_boundary.output
  1   libs/locale/test/test_formatting.test/gcc-4.8/debug/test_formatting.output
200   
libs/heap/test/binomial_heap_test.test/gcc-4.8/debug/threading-multi/binomial_heap_test.output
200   
libs/heap/test/priority_queue_test.test/gcc-4.8/debug/threading-multi/priority_queue_test.output
200   
libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output
200   
libs/heap/test/fibonacci_heap_test.test/gcc-4.8/debug/threading-multi/fibonacci_heap_test.output
200   
libs/heap/test/mutable_heap_test.test/gcc-4.8/debug/threading-multi/mutable_heap_test.output
200   
libs/heap/test/skew_heap_test.test/gcc-4.8/debug/threading-multi/skew_heap_test.output
200   
libs/heap/test/pairing_heap_tests.test/gcc-4.8/debug/threading-multi/pairing_heap_tests.output



So, Boost 1.55 on amd64 does have errors. However, less than on PPC/64. And no 
test running in an infinite loop, though there are several on PPC/64.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276262

Title:
  Many tests of Boost v1.54 fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.54/+bug/1276262/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1276262] Re: Many tests of Boost v1.54 fail

2014-02-14 Thread Tony Reix

Here is the same report about Boost 1.55 on Ubuntu 14.04 PPC/LE .

4214 tests

libs/math/test/test_jacobi.test/gcc-4.8/debug/link-static/test_jacobi.output
libs/heap/test/d_ary_heap_test.test/gcc-4.8/debug/threading-multi/d_ary_heap_test.output
libs/heap/test/skew_heap_test.test/gcc-4.8/debug/threading-multi/skew_heap_test.output
libs/heap/test/pairing_heap_tests.test/gcc-4.8/debug/threading-multi/pairing_heap_tests.output
libs/heap/test/fibonacci_heap_test.test/gcc-4.8/debug/threading-multi/fibonacci_heap_test.output
libs/heap/test/mutable_heap_test.test/gcc-4.8/debug/threading-multi/mutable_heap_test.output
libs/heap/test/priority_queue_test.test/gcc-4.8/debug/threading-multi/priority_queue_test.output
libs/heap/test/binomial_heap_test.test/gcc-4.8/debug/threading-multi/binomial_heap_test.output
Number of Memory Access Violation:  8


  0 4045
  1   28
1341
1395
2009
201  115
-
Tot 4204

Number of sub-failures:  59818

Cores:
libs/log/test/core.test/gcc-4.8/debug/build-no/threading-multi/core
libs/phoenix/test/core.test/gcc-4.8/debug/core


201   libs/tr1/test/run_random.test/gcc-4.8/debug/run_random.output
201   libs/tr1/test/std_run_random.test/gcc-4.8/debug/std_run_random.output
139   
libs/context/test/test_context.test/gcc-4.8/debug/link-static/test_context.output
200   libs/test/test/prg_exec_fail1.test/gcc-4.8/debug/prg_exec_fail1.output
201   libs/test/test/test_tools_test.test/gcc-4.8/debug/test_tools_test.output
  1   libs/test/test/prg_exec_fail4.test/gcc-4.8/debug/prg_exec_fail4.output
200   libs/test/test/prg_exec_fail3.test/gcc-4.8/debug/prg_exec_fail3.output
201   libs/test/test/minimal_test.test/gcc-4.8/debug/minimal_test.output
201   
libs/ptr_container/test/serialization.test/gcc-4.8/debug/serialization.output
201   
libs/conversion/test/lexical_cast_inf_nan_test.test/gcc-4.8/debug/link-static/lexical_cast_inf_nan_test.output
201   
libs/conversion/test/lexical_cast_loopback_test.test/gcc-4.8/debug/link-static/lexical_cast_loopback_test.output
201   
libs/conversion/test/lexical_cast_float_types_test.test/gcc-4.8/debug/link-static/lexical_cast_float_types_test.output
201   libs/geometry/test/algorithms/expand.test/gcc-4.8/debug/expand.output
201   libs/geometry/test/algorithms/area.test/gcc-4.8/debug/area.output
201   
libs/geometry/test/algorithms/difference.test/gcc-4.8/debug/difference.output
201   libs/geometry/test/algorithms/union.test/gcc-4.8/debug/union.output
201   
libs/geometry/test/algorithms/overlay/traverse.test/gcc-4.8/debug/traverse.output
201   
libs/geometry/test/algorithms/overlay/self_intersection_points.test/gcc-4.8/debug/self_intersection_points.output
201   
libs/geometry/test/algorithms/overlay/get_turns.test/gcc-4.8/debug/get_turns.output
201   
libs/geometry/test/algorithms/overlay/ccw_traverse.test/gcc-4.8/debug/ccw_traverse.output
201   
libs/geometry/test/algorithms/intersection.test/gcc-4.8/debug/intersection.output
201   libs/geometry/test/algorithms/within.test/gcc-4.8/debug/within.output
201   libs/geometry/test/algorithms/centroid.test/gcc-4.8/debug/centroid.output
201   
libs/geometry/test/multi/algorithms/multi_difference.test/gcc-4.8/debug/multi_difference.output
201   
libs/geometry/test/multi/algorithms/multi_union.test/gcc-4.8/debug/multi_union.output
201   
libs/geometry/test/multi/algorithms/multi_intersection.test/gcc-4.8/debug/multi_intersection.output
201   
libs/math/test/test_nc_chi_squared_double.test/gcc-4.8/debug/link-static/test_nc_chi_squared_double.output
201   libs/math/test/test_erf.test/gcc-4.8/debug/link-static/test_erf.output
201   
libs/math/test/test_bessel_y.test/gcc-4.8/debug/link-static/test_bessel_y.output
201   
libs/math/test/test_ibeta_real_concept1.test/gcc-4.8/debug/link-static/test_ibeta_real_concept1.output
201   
libs/math/test/test_triangular.test/gcc-4.8/debug/link-static/test_triangular.output
201   
libs/math/test/test_owens_t.test/gcc-4.8/debug/link-static/test_owens_t.output
201   
libs/math/test/test_legendre.test/gcc-4.8/debug/link-static/test_legendre.output
201   
libs/math/test/test_binomial_long_double.test/gcc-4.8/debug/link-static/test_binomial_long_double.output
201   
libs/math/test/test_ibeta_inv_long_double.test/gcc-4.8/debug/link-static/test_ibeta_inv_long_double.output
201   libs/math/test/test_cbrt.test/gcc-4.8/debug/link-static/test_cbrt.output
201   
libs/math/test/test_spherical_harmonic.test/gcc-4.8/debug/link-static/test_spherical_harmonic.output
201   
libs/math/test/test_digamma.test/gcc-4.8/debug/link-static/test_digamma.output
201   
libs/math/test/test_nc_beta_double.test/gcc-4.8/debug/link-static/test_nc_beta_double.output
201   
libs/math/test/test_fisher_f.test/gcc-4.8/debug/link-static/test_fisher_f.output
201   libs/math/test/test_round.test/gcc-4.8/debug/link-static/test_round.output
201   
libs/math/test/test_ibeta_inv_real_concept1.test/gcc-4.8/debug/link-static/test_ibeta_inv_real_concept1.output
201   
libs/math/test/test_nc_beta_long_double.test/gcc-4.8/d

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

I've tried to use PDb on Ubuntu/PPC64LE for debugging the issue.

However, with Pdb, the issue disappears...
We have in "opts" variable the correct value for fields: 'fields': 'first, 
last'


$ pdb ../../lang/py/build/scripts/avro cat /tmp/REIX --fields 'first, last'

build/scripts/avro: line 243:
  opts, args = parser.parse_args(argv[1:])

Pdb) c
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(243)main()
-> opts, args = parser.parse_args(argv[1:])
(Pdb) n
...
(Pdb) p opts

(Pdb) p args
['cat', '/tmp/REIX']


...

(Pdb) n
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(125)cat()
-> print_avro(avro, opts)
(Pdb) n
{"last": "duck", "first": "daffy"}
{"last": "bunny", "first": "bugs"}
{"last": "", "first": "tweety"}
{"last": "runner", "first": "road"}
{"last": "e", "first": "wile"}
{"last": "le pew", "first": "pepe"}
{"last": "leghorn", "first": "foghorn"}
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(113)cat()
-> for filename in args:
(Pdb) n
--Return--
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(113)cat()->None
-> for filename in args:
(Pdb) n
--Return--
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(250)main()->None
-> cat(opts, args)
(Pdb) n
--Return--
> /home/tony/AVRO/avro-FromFreshIBMSOEGitHub/lang/py/build/scripts/avro(261)()->None
-> main()
(Pdb) n
--Return--
> (1)()->None
(Pdb) n
The program finished and will be restarted


Launching the same command withoug pdb:
../../lang/py/build/scripts/avro cat /tmp/REIX --fields 'first, last'
raised the same issue:

{"first": "daffy"}
{"first": "bugs"}
{"first": "tweety"}
{"first": "road"}
{"first": "wile"}
{"first": "pepe"}
{"first": "foghorn"}
Usage: avro cat|write [options] FILE [FILE...]

avro: error: Can't open last - [Errno 2] No such file or directory:
'last'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

Looking at ./Lib/optparse.py of Python 2.7.6 :
   def parse_args(self, args=None, values=None):

   stop = self._process_args(largs, rargs, values)

  _process_args()
   _process_args()
   _process_long_opt()

Probably the issue is in :

def _process_long_opt(self, rargs, values):
 ...

??

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

Hi Breno
OK. There is a place where to get an install image for Ubuntu 14.10 for PPC64 
LE.
Since the PPC64/LE machines I use are managed by another team, it may be 
complicated/long to get them agree to install a machine with something 
unstable. Anyway, I'll ask if it is possible.

Now, why do you think that the issue is in the Ubuntu system and not simply in 
the port of the Python 2.7.6 on PPC64/LE ?
I don't know a lot about Python, however I guess that there is probably C code 
that may have an issue.

I'll probably check with other versions of Python 2, in order to know if
the issue is specific to some sub-version of Python 2, or only to this
2.7.6 .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

No issue with Python. My mistake.

** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1378888] Re: OptionParser on PPC64LE does not split args correctly

2014-10-09 Thread Tony Reix

I've found the issue. I had changed the python shell in order to add some trace 
options and that generated the issue. Removing the change did fix the issue. 
And, looking in depth at Avro results, I found that the final result is mixed 
with the traces, and that the result is OK.
So, that is my mistake. Sorry. Gonna close the defect.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/137

Title:
  OptionParser on PPC64LE does not split args correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/137/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

39 matches

Mail list logo