Bug 2797 - Segmentation fault when logging level is FINEST
Summary: Segmentation fault when logging level is FINEST
Status: RESOLVED INVALID
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Andrew Cagney
URL:
Keywords:
Depends on:
Blocks: 2188
  Show dependency tree / graph
 
Reported: 2006-06-19 06:18 UTC by Yao Qi
Modified: 2006-07-11 15:38 UTC (History)
0 users

See Also:
Host: ppc64-redhat-linux
Target: ppc64-redhat-linux
Build: ppc64-redhat-linux
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yao Qi 2006-06-19 06:18:55 UTC 
build cvs head on ppc64(FC5), and got segmentation fault when logging level is
FINEST,

[qiyao@plinuxt18 frysk-core]$ ./TestRunner -l FINEST frysk.proc.TestExec
Running testProcBlockExec(frysk.proc.TestExec) ...28585.28585:
argv[0]=/home/qiyao/build-frysk-5-23/frysk-core/frysk/pkglibexecdir/funit-child
28585.28585: argv[1]=--wait=suspend
28585.28585: argv[2]=10
28585.28585: argv[3]=28582
28585.28585: argv[4]=/bin/rm
28585.28585: argv[5]=./frysk.proc.TestExec.xcfduz.tmp
28585.28585: starting 28585
28585.28585: new thread 28585.28585
28585.28585: notify 28582 with 10 (User defined signal 1) -- new thread 28585.28585
Segmentation fault
[qiyao@plinuxt18 frysk-core]$ 28585.28585: received signal 14 (Alarm clock)
28585.28585: exit

All test cases could pass on X86.
Comment 1 Yao Qi 2006-06-19 10:05:07 UTC 
Run make distclean  in build directory, and rebuilt it, no such problem any more!