[#6810] libmudflap.c has some output pattern test failure frequently

Document created by Aaronwu Employee on Oct 17, 2013
Version 1Show Document
  • View in full screen mode

[#6810] libmudflap.c has some output pattern test failure frequently

Submitted By: Mingquan Pan

Open Date

2011-10-10 02:58:35     Close Date

2012-03-12 11:47:35

Priority:

Low     Assignee:

Mingquan Pan

Stuart Henderson

Board:

N/A     Silicon Revision:

Resolution:

Fixed     Fixed In Release:

2012R1

Processor:

ALL     

Host Operating System:

toolchain rev.:

    kernel rev.:

State:

Closed     Found In Release:

N/A

Is this bug repeatable?:

N/A     

Summary: libmudflap.c has some output pattern test failure frequently

Details:

 

libmudflap.c has some output pattern test failure frequently now.

 

on bf561-ezkit, there are some output pattern test failure, but it vary from time to time.

 

#########################################

#

# Comparing libmudflap-4.3.sum

#

########################################

Tests that now fail, but worked before:

 

bfin-uclinux: libmudflap.c/fail10-frag.c (-O2) output pattern test

bfin-uclinux: libmudflap.c/fail11-frag.c (-O3) output pattern test

bfin-uclinux: libmudflap.c/fail13-frag.c (-O2) output pattern test

bfin-uclinux: libmudflap.c/fail14-frag.c output pattern test

bfin-uclinux: libmudflap.c/fail14-frag.c (-static) output pattern test

bfin-uclinux: libmudflap.c/fail18-frag.c (-O3) output pattern test

bfin-uclinux: libmudflap.c/fail21-frag.c (-O2) output pattern test

bfin-uclinux: libmudflap.c/fail26-frag.c output pattern test

bfin-uclinux: libmudflap.c/fail28-frag.c (-O2) output pattern test

bfin-uclinux: libmudflap.c/fail29-frag.c (-O3) output pattern test

bfin-uclinux: libmudflap.c/fail31-frag.c output pattern test

bfin-uclinux: libmudflap.c/fail36-frag.c (-static) output pattern test

bfin-uclinux: libmudflap.c/fail39-frag.c (-static) output pattern test

bfin-uclinux: libmudflap.c/fail4-frag.c (-O2) output pattern test

bfin-uclinux: libmudflap.c/fail5-frag.c (-static) output pattern test

bfin-uclinux: libmudflap.c/fail6-frag.c (-O3) output pattern test

bfin-uclinux: libmudflap.cth/pass40-frag.c (-static -DSTATIC) execution test

 

Executing on bfin-uclinux: /tmp/fail10-frag.exe.19497    (timeout = 300)

*******

mudflap violation 1 (check/write): time=1314929013.343376 ptr=0x5e3ebc size=1

pc=0x509d3e location=`/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libmudflap/testsuite/libmudflap.c/fail10-frag.c:10:1 (main)'

      [0x0x508ca0]

Nearby object 1: checked region begins 1B after and ends 1B after

mudflap SEGV

XYZ139ZYX

object 0x2e176e8: name=`/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libmudflap/testsuite/libmudflap.c/fail10-frag.c:6:14 (main) foo'

bounds=[0x5e3e94,0x5e3ebb] size=40 area=stack check=0r/0w liveness=0

alloc time=1314929013.343353 pc=0x5098fe

number of nearby objects: 1

Executing on bfin-uclinux: rm -f  /tmp/fail10-frag.exe.19497    (timeout = 300)

XYZ0ZYX

Executed ./fail10-frag.exe, status 1

*******

mudflap violation 1 (check/write): time=1314929013.343376 ptr=0x5e3ebc size=1

pc=0x509d3e location=`/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libmudflap/testsuite/libmudflap.c/fail10-frag.c:10:1 (main)'

      [0x0x508ca0]

Nearby object 1: checked region begins 1B after and ends 1B after

mudflap SEGV

object 0x2e176e8: name=`/home/test/work/cruise/checkouts/toolchain/gcc-4.3/libmudflap/testsuite/libmudflap.c/fail10-frag.c:6:14 (main) foo'

bounds=[0x5e3e94,0x5e3ebb] size=40 area=stack check=0r/0w liveness=0

alloc time=1314929013.343353 pc=0x5098fe

number of nearby objects: 1

PASS: libmudflap.c/fail10-frag.c (-O2) crash test

FAIL: libmudflap.c/fail10-frag.c (-O2) output pattern test

Output pattern mudflap violation 1.*Nearby object 1.*mudflap object.*.main. foo.*

 

Follow-ups

 

--- Stuart Henderson                                         2011-10-10 05:39:47

the expected output:

"mudflap object.*.main. foo.*"

is being interrupted by a SEGV:

"mudflap SEGV

XYZ139ZYX

object 0x2e176e8"

 

the output is correct and we have no control over when the SEGV appears so it's

purely a testsuite bug.

I don't plan to spend any time on this any time soon.

 

downgrading to low.

 

--- Sonic Zhang                                              2011-10-10 22:34:25

Do you mean Grace should fix the test case to make it pass under this pattern?

 

--- Stuart Henderson                                         2011-10-11 05:23:44

i believe the SEGV could occur at any point in the output, so there is no easy

fix like that.

 

--- Stuart Henderson                                         2012-03-12 12:30:38

I believe i've fixed this a little while back, and there's another tracker that

covers this anyway.

 

Closing as fixed.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

No Files Were Found

Attachments

    Outcomes