[lkml]   [2010]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectFloating point exception by perf record

    Hi Arnaldo,

    I suffered a mysterious floating point exception when executing perf
    on current tip/master.

    For example,

    % sudo ./perf lock record ./perf bench sched messaging
    # Running sched/messaging benchmark...
    # 20 sender and receiver processes per group
    # 10 groups == 400 processes run

    Total time: 1.375 [sec]
    [ perf record: Woken up 0 times to write data ]
    [ perf record: Captured and wrote 160.002 MB (~6990599 samples) ]
    [1] 26348 floating point exception sudo ./perf lock record ./perf
    bench sched messaging

    dmesg says that

    [10212.752490] perf[26348] trap divide error ip:7fade8564310
    sp:7fff46d926e8 error:0 in[7fade8556000+15000]

    Example is of perf lock, but this is not a special phenomenon of perf lock,
    other users of perf record, like perf sched, caused the same problem.

    I found that this might be caused by the line 283 of perf.c

    if (fclose(stdout)) # <- closing stdout!
    die("close failed on standard output: %s", strerror(errno));

    I don't know well about libnewt, do you know something like cause?

    The version of libnewt I'm using is 0.52.2 (default of Debian lenny)


     \ /
      Last update: 2010-04-04 10:13    [W:0.020 / U:33.592 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site