1>segmentation fault error:
When I ran runtest/math with runltp, the float cases worked well.
But they would drop into segmentation fault when they were called directly
in command line.

# cat runtest/math
.........
float_bessel cd $LTPROOT/testcases/bin; float_bessel -v
float_exp_log cd $LTPROOT/testcases/bin; float_exp_log -v
float_iperb cd $LTPROOT/testcases/bin; float_iperb -v
float_power cd $LTPROOT/testcases/bin; float_power -v
float_trigo cd $LTPROOT/testcases/bin; float_trigo -v
.........

# ./runltp -f math
# cat result/xxxx.log
Test Start Time: Fri Sep 12 15:23:47 2008
-----------------------------------------
Testcase                       Result     Exit Value
--------                       ------     ----------
abs01                          PASS       0
atof01                         PASS       0
float_bessel                   PASS       0
float_exp_log                  PASS       0
float_iperb                    PASS       0
float_power                    PASS       0
float_trigo                    PASS       0
fptest01                       PASS       0
fptest02                       PASS       0
nextafter01                    PASS       0

-----------------------------------------------
Total Tests: 10
Total Failures: 0
Kernel Version: 2.6.18-92.el5
Machine Architecture: i686
Hostname: gjb.cn.ibm.com


# cd testcases/bin/
# ./float_bessel -v
Segmentation fault

The reason is to input "NULL" to strlen() which caused Segmentation fault.

2> memory leaks:
Another,  the patch also fixed a large number of  memory leaks in
math/float cases.
===============
Before Patching
===============
# cd testcases/bin/
# valgrind --leak-check=full --show-reachable=yes ./float_bessel -v

==32529== LEAK SUMMARY:
==32529==    definitely lost: 160,000 bytes in 1 blocks.
==32529==      possibly lost: 33,440,136 bytes in 220 blocks.
==32529==    still reachable: 51,009 bytes in 109 blocks.
==32529==         suppressed: 0 bytes in 0 blocks.

===============
After Patching
===============
# valgrind --leak-check=full --show-reachable=yes ./float_bessel -v

==2597== LEAK SUMMARY:
==2597==    definitely lost: 0 bytes in 0 blocks.
==2597==      possibly lost: 0 bytes in 0 blocks.
==2597==    still reachable: 979 bytes in 6 blocks.
==2597==         suppressed: 0 bytes in 0 blocks.

Signed-off-by: Jin Bing Guo <[EMAIL PROTECTED]>
---------------
(See attached file: Fix_mem_leak_float_main.patch)(See attached file:
Fix_mem_leak_thread_code.patch)


Best regards!

Jin Bing Guo  郭晋兵

Linux for System p Test
IBM China Systems & Technology Laboratory in Beijing
Tel:   +86-10-82454439
Email: [EMAIL PROTECTED]
-------------------------------------
"Do today what others won't so tomorrow you do what other's can't"

Attachment: Fix_mem_leak_float_main.patch
Description: Binary data

Attachment: Fix_mem_leak_thread_code.patch
Description: Binary data

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to