You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by "Andrew Black (JIRA)" <ji...@apache.org> on 2007/09/27 21:54:50 UTC

[jira] Created: (STDCXX-573) Enable building with Purify

Enable building with Purify
---------------------------

                 Key: STDCXX-573
                 URL: https://issues.apache.org/jira/browse/STDCXX-573
             Project: C++ Standard Library
          Issue Type: Improvement
          Components: Build
            Reporter: Andrew Black
            Priority: Minor
             Fix For: 4.2.1


It would be useful to be able to build and run the examples, utilities and tests using Rational Purify.  This could potentially allow us to detect errors, such as memory leaks, which we might not otherwise detect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (STDCXX-573) Enable building with Purify

Posted by "Andrew Black (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STDCXX-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Black updated STDCXX-573:
--------------------------------

    Attachment: purify.diff

Attached (As purify.diff) is my first take at resolving this issue, though there are a few things that need to be fixed before the patch is included.  I targeted this issue at 4.2.1, as it's too late in the 4.2.0 cycle for this sort of change.

One major issue is that it doesn't instrument the utilities (exec, locale/localedef), and this likely would be desired.  A second issue is that we'd want to update the windows infrastructure for feature parity.

A smaller issue is that we need to determine the correct behavior if a user defines both PHDIR and PURE_OPTS.  We may also wish to consider increasing the timeout used when running the tests and examples.

Probably one other issue to consider is whether this should be extended to single step compilation and single step run compilation.

Changelog:

2007-09-27 Andrew Black <ab...@roguewave.com>
* GNUmakefile: Document PURE_OPTS flag, add to generated makefile.in.
* makefile.rules [PURE_OPTS]: Link executables using purify if PURE_OPTS is defined.

> Enable building with Purify
> ---------------------------
>
>                 Key: STDCXX-573
>                 URL: https://issues.apache.org/jira/browse/STDCXX-573
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Andrew Black
>            Priority: Minor
>             Fix For: 4.2.1
>
>         Attachments: purify.diff
>
>
> It would be useful to be able to build and run the examples, utilities and tests using Rational Purify.  This could potentially allow us to detect errors, such as memory leaks, which we might not otherwise detect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (STDCXX-573) Enable building with Purify

Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/STDCXX-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sebor reassigned STDCXX-573:
-----------------------------------

    Assignee: Travis Vitek

Adding Purify to our nightly testing would be worthwhile, as would running valgrind on Linux.
Travis, you might want to look at this to see if it makes sense.

> Enable building with Purify
> ---------------------------
>
>                 Key: STDCXX-573
>                 URL: https://issues.apache.org/jira/browse/STDCXX-573
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 4.2.0
>            Reporter: Andrew Black
>            Assignee: Travis Vitek
>            Priority: Minor
>             Fix For: 4.2.1
>
>         Attachments: purify.diff
>
>
> It would be useful to be able to build and run the examples, utilities and tests using Rational Purify.  This could potentially allow us to detect errors, such as memory leaks, which we might not otherwise detect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.