Opened 13 years ago

Closed 13 years ago

#3542 closed Bugs (duplicate)

Bug in documentation of detect_memory_leak parameter

Reported by: mloskot <mateusz@…> Owned by: Gennadiy Rozental
Milestone: Boost 1.41.0 Component: test
Version: Boost 1.40.0 Severity: Problem
Keywords: Cc:

Description

On the UTF manual page Runtime parameters reference (Boost 1.40.0), there is mistake in parameter detect_memory_leak section. Currently, it says

Command line argument name: 	build_info

but should read:

Command line argument name: 	detect_memory_leak

Change History (2)

comment:1 by mloskot <mateusz@…>, 13 years ago

By the way, I've also noticed that the name of parameter is incorrect and it should be detect_memory_leaks. If I ask to disable memory leak with _leak' version the leaks are still being detected:

C:\>test.exe --detect_memory_leak=0
Test setup error: test tree is empty
Detected memory leaks!
Dumping objects ->
{211} normal block at 0x027FA3E8, 516 bytes long.
 Data: <                > 00 00 00 00 00 00 00 00 00 00 00 00 F4 01 00 00
{210} normal block at 0x027FA2B8, 256 bytes long.
 Data: <                > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Object dump complete.

but if I try _leaks variant of the parameter, leaks check are effectively disabled:

C:\>test.exe --detect_memory_leaks=0
Test setup error: test tree is empty

comment:2 by Gennadiy Rozental, 13 years ago

Resolution: duplicate
Status: newclosed

Duplicates #2018

Note: See TracTickets for help on using tickets.