#60 lcov fails to locate sources

closed-accepted
mreed
Tools (21)
7
2007-07-09
2004-12-28
No

when running lcov over an uninstalled user-space apps
tests, it finds the .da file in the .libs directories,
but does not look for the sources one hierarchy up.
Libtool places the object in the .libs dirs. when
running gcov manually one can specify -o.libs/ to
produce a source.c.gov file.

Discussion

  • Robert Williamson

    • assigned_to: nobody --> mridge
     
  • Stefan Sauer

    Stefan Sauer - 2005-07-04

    Logged In: YES
    user_id=250654

    I now have attached a patch that fixes the problem for me.
    please do not just ignore this report. the lcov tool is so
    nice and it would be a shame if it can not be used for
    normal apps.

     
  • Stefan Sauer

    Stefan Sauer - 2005-07-04
    • priority: 5 --> 7
     
  • Stefan Sauer

    Stefan Sauer - 2005-07-04

    fixes file lookup to understand .libs files

     
  • Robert Williamson

    • assigned_to: mridge --> robbiew
    • status: open --> closed-fixed
     
  • Robert Williamson

    Logged In: YES
    user_id=236704

    Thanks for the patch and sorry for the delay. I've applied
    the patch to the CVS tree.

     
  • Thomas Vander Stichele

    Logged In: YES
    user_id=197434

    This is broken again in 1.6pre1 - I just tried it. The
    patch doesn't apply anymore, and it seems some reworking has
    been done on the location of various files.

    We really would like to use lcov in a lot of projects, but
    all of them use autotools and libtool.

    If you want a simple sample project to verify this with,
    there's:
    https://apestaart.org/thomas/trac/browser/tests/gcov

     
  • Robert Williamson

    • assigned_to: robbiew --> mreed10
    • status: closed-fixed --> open
     
  • Subrata Modak

    Subrata Modak - 2007-05-16
    • status: open --> closed-out-of-date
     
  • Peter Oberparleiter

    Logged In: YES
    user_id=586057
    Originator: NO

    The cvs versions of lcov (1.6-pre1) supports a new command line parameter '--compat-libtool' which, when specified, will trigger the requested behavior.

     
  • Stefan Sauer

    Stefan Sauer - 2007-07-01
    • status: closed-out-of-date --> open-out-of-date
     
  • Stefan Sauer

    Stefan Sauer - 2007-07-01

    Logged In: YES
    user_id=250654
    Originator: YES

    On sf.net is only lcov 1.5 and its still unpatched. Guys PLEASE apply the match and make a release.

     
  • Stefan Sauer

    Stefan Sauer - 2007-07-01

    Logged In: YES
    user_id=250654
    Originator: YES

    Why the heck '--compat-libtool', this can be enabled by default. It does not cause any harm. If you think otherwise, please explain. I am now going to test the cvs version.

     
  • Stefan Sauer

    Stefan Sauer - 2007-07-01

    Logged In: YES
    user_id=250654
    Originator: YES

    something is totally messed up here. cvs (utils/analysis/lcov) has 1.5 too.

     
  • Stefan Sauer

    Stefan Sauer - 2007-07-02

    Logged In: YES
    user_id=250654
    Originator: YES

    Thanks for the link to the discussion. Actually I don't think its a hack to look into the parent directory of ".libs" - that is how libtool works. bu okay, I'll wait for 1.6 and then add the switch.

    Stefan

     
  • Subrata Modak

    Subrata Modak - 2007-07-09
    • status: open-out-of-date --> closed-accepted
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks