Skip to content

Commit 7fe34bf

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)
2 parents 8c8c6d5 + 61dc40d commit 7fe34bf

21 files changed

+609
-600
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6712,6 +6712,11 @@
67126712
"redirect_url": "/visualstudio/mac/",
67136713
"redirect_document_id": false
67146714
},
6715+
{
6716+
"source_path": "mac/activation.md",
6717+
"redirect_url": "/visualstudio/mac/enable-subscription",
6718+
"redirect_document_id": false
6719+
},
67156720
{
67166721
"source_path": "docs/cross-platform/overview-of-visual-studio-tools-for-unity.md",
67176722
"redirect_url": "/visualstudio/cross-platform/visual-studio-tools-for-unity",

docs/debugger/c-cpp-assertions.md

Lines changed: 196 additions & 196 deletions
Large diffs are not rendered by default.

docs/debugger/debug-interface-access/constants-debug-interface-access-sdk.md

Lines changed: 42 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -2,55 +2,55 @@
22
title: "Constants (Debug Interface Access SDK) | Microsoft Docs"
33
ms.date: "11/04/2016"
44
ms.topic: "conceptual"
5-
dev_langs:
5+
dev_langs:
66
- "C++"
7-
helpviewer_keywords:
7+
helpviewer_keywords:
88
- "constants, DIA SDK"
99
- "DIA SDK, constants"
1010
ms.assetid: aca4ec77-bc08-4cdd-a6ce-8d4a28ea5ea3
1111
author: "mikejo5000"
1212
ms.author: "mikejo"
1313
manager: jillfra
14-
ms.workload:
14+
ms.workload:
1515
- "multiple"
1616
---
1717
# Constants (Debug Interface Access SDK)
18-
These string constants can be used to identify various sections of a program debug database (PDB) file through the DIA SDK.
19-
20-
## Constants
21-
The following are declared as C/C++ macros.
22-
23-
|Macro|Value|
24-
|-----------|-----------|
25-
|`DiaTable_Symbols`|L"Symbols"|
26-
|`DiaTable_Sections`|L"Sections"|
27-
|`DiaTable_SrcFiles`|L"SourceFiles"|
28-
|`DiaTable_LineNums`|L"LineNumbers"|
29-
|`DiaTable_SegMap`|L"SegmentMap"|
30-
|`DiaTable_Dbg`|L"Dbg"|
31-
|`DiaTable_InjSrc`|L"InjectedSource"|
32-
|`DiaTable_FrameData`|L"FrameData"|
33-
34-
## Example
35-
Here is an example using one of these symbols:
36-
37-
```C++
38-
HRESULT GetSymbolTable(IDiaEnumTables *pEnumTables, IDiaTable **pTable)
39-
{
40-
HRESULT hr;
41-
VARIANT var;
42-
var.vt = VT_BSTR;
43-
var.bstrVal = SysAllocString( DiaTable_Symbols );
44-
hr = pEnumTables->Item( var, pTable );
45-
return(hr);
46-
}
47-
```
48-
49-
## Requirements
50-
Header: dia2.h
51-
52-
## See Also
53-
[Reference](../../debugger/debug-interface-access/debug-interface-access-sdk-reference.md)
54-
[Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
55-
[Interfaces (Debug Interface Access SDK)](../../debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md)
56-
[IDiaEnumTables::Item](../../debugger/debug-interface-access/idiaenumtables-item.md)
18+
These string constants can be used to identify various sections of a program debug database (PDB) file through the DIA SDK.
19+
20+
## Constants
21+
The following are declared as C/C++ macros.
22+
23+
|Macro|Value|
24+
|-----------|-----------|
25+
|`DiaTable_Symbols`|L"Symbols"|
26+
|`DiaTable_Sections`|L"Sections"|
27+
|`DiaTable_SrcFiles`|L"SourceFiles"|
28+
|`DiaTable_LineNums`|L"LineNumbers"|
29+
|`DiaTable_SegMap`|L"SegmentMap"|
30+
|`DiaTable_Dbg`|L"Dbg"|
31+
|`DiaTable_InjSrc`|L"InjectedSource"|
32+
|`DiaTable_FrameData`|L"FrameData"|
33+
34+
## Example
35+
Here is an example using one of these symbols:
36+
37+
```C++
38+
HRESULT GetSymbolTable(IDiaEnumTables *pEnumTables, IDiaTable **pTable)
39+
{
40+
HRESULT hr;
41+
VARIANT var;
42+
var.vt = VT_BSTR;
43+
var.bstrVal = SysAllocString( DiaTable_Symbols );
44+
hr = pEnumTables->Item( var, pTable );
45+
return(hr);
46+
}
47+
```
48+
49+
## Requirements
50+
Header: dia2.h
51+
52+
## See Also
53+
[Reference](../../debugger/debug-interface-access/debug-interface-access-sdk-reference.md)
54+
[Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
55+
[Interfaces (Debug Interface Access SDK)](../../debugger/debug-interface-access/interfaces-debug-interface-access-sdk.md)
56+
[IDiaEnumTables::Item](../../debugger/debug-interface-access/idiaenumtables-item.md)

docs/debugger/debug-interface-access/idiadatasource-loadandvalidatedatafrompdb.md

Lines changed: 75 additions & 75 deletions
Original file line numberDiff line numberDiff line change
@@ -2,87 +2,87 @@
22
title: "IDiaDataSource::loadAndValidateDataFromPdb | Microsoft Docs"
33
ms.date: "11/04/2016"
44
ms.topic: "conceptual"
5-
dev_langs:
5+
dev_langs:
66
- "C++"
7-
helpviewer_keywords:
7+
helpviewer_keywords:
88
- "IDiaDataSource::loadAndValidateDataFromPdb method"
99
ms.assetid: d66712dd-6c24-4192-919a-cce262066f0e
1010
author: "mikejo5000"
1111
ms.author: "mikejo"
1212
manager: jillfra
13-
ms.workload:
13+
ms.workload:
1414
- "multiple"
1515
---
1616
# IDiaDataSource::loadAndValidateDataFromPdb
17-
Opens and verifies that the program database (.pdb) file matches the signature information provided, and prepares the .pdb file as a debug data source.
18-
19-
## Syntax
20-
21-
```C++
22-
HRESULT loadAndValidateDataFromPdb
23-
LPCOLESTR pdbPath,
24-
GUID* pcsig70,
25-
DWORD sig,
26-
DWORD age
27-
);
28-
```
29-
30-
#### Parameters
31-
`pdbPath`
32-
[in] The path to the .pdb file.
33-
34-
`pcsig70`
35-
[in] The GUID signature to verify against the .pdb file signature. Only .pdb files in [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] and later have GUID signatures.
36-
37-
`sig`
38-
[in] The 32-bit signature to verify against the .pdb file signature.
39-
40-
`age`
41-
[in] Age value to verify. The age does not necessarily correspond to any known time value, it is used to determine if a .pdb file is out of sync with a corresponding .exe file.
42-
43-
## Return Value
44-
If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.
45-
46-
|Value|Description|
47-
|-----------|-----------------|
48-
|E_PDB_NOT_FOUND|Failed to open the file, or the file has an invalid format.|
49-
|E_PDB_FORMAT|Attempted to access a file with an obsolete format.|
50-
|E_PDB_INVALID_SIG|Signature does not match.|
51-
|E_PDB_INVALID_AGE|Age does not match.|
52-
|E_INVALIDARG|Invalid parameter.|
53-
|E_UNEXPECTED|The data source has already been prepared.|
54-
55-
## Remarks
56-
A .pdb file contains both signature and age values. These values are replicated in the .exe or .dll file that matches the .pdb file. Before preparing the data source, this method verifies that the named .pdb file's signature and age match the values provided.
57-
58-
To load a .pdb file without validation, use the [IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md) method.
59-
60-
To gain access to the data load process (through a callback mechanism), use the [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md) method.
61-
62-
To load a .pdb file directly from memory, use the [IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md) method.
63-
64-
## Example
65-
66-
```C++
67-
IDiaDataSource* pSource; // Previously created data source.
68-
DEFINE_GUID(expectedGUIDSignature,0x1234,0x5678,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08);
69-
DWORD expectedFileSignature = 0x12345678;
70-
DWORD expectedAge = 128;
71-
72-
HRESULT hr;
73-
hr = pSource->loadAndValidateDataFromPdb( L"yprog.pdb",
74-
&expectedGUIDSignature,
75-
expectedFileSignature,
76-
expectedAge);
77-
if (FAILED(hr))
78-
{
79-
// Report an error
80-
}
81-
82-
```
83-
84-
## See Also
85-
[IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)
86-
[IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md)
87-
[IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md)
88-
[IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md)
17+
Opens and verifies that the program database (.pdb) file matches the signature information provided, and prepares the .pdb file as a debug data source.
18+
19+
## Syntax
20+
21+
```C++
22+
HRESULT loadAndValidateDataFromPdb
23+
LPCOLESTR pdbPath,
24+
GUID* pcsig70,
25+
DWORD sig,
26+
DWORD age
27+
);
28+
```
29+
30+
#### Parameters
31+
`pdbPath`
32+
[in] The path to the .pdb file.
33+
34+
`pcsig70`
35+
[in] The GUID signature to verify against the .pdb file signature. Only .pdb files in [!INCLUDE[vcprvc](../../code-quality/includes/vcprvc_md.md)] and later have GUID signatures.
36+
37+
`sig`
38+
[in] The 32-bit signature to verify against the .pdb file signature.
39+
40+
`age`
41+
[in] Age value to verify. The age does not necessarily correspond to any known time value, it is used to determine if a .pdb file is out of sync with a corresponding .exe file.
42+
43+
## Return Value
44+
If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.
45+
46+
|Value|Description|
47+
|-----------|-----------------|
48+
|E_PDB_NOT_FOUND|Failed to open the file, or the file has an invalid format.|
49+
|E_PDB_FORMAT|Attempted to access a file with an obsolete format.|
50+
|E_PDB_INVALID_SIG|Signature does not match.|
51+
|E_PDB_INVALID_AGE|Age does not match.|
52+
|E_INVALIDARG|Invalid parameter.|
53+
|E_UNEXPECTED|The data source has already been prepared.|
54+
55+
## Remarks
56+
A .pdb file contains both signature and age values. These values are replicated in the .exe or .dll file that matches the .pdb file. Before preparing the data source, this method verifies that the named .pdb file's signature and age match the values provided.
57+
58+
To load a .pdb file without validation, use the [IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md) method.
59+
60+
To gain access to the data load process (through a callback mechanism), use the [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md) method.
61+
62+
To load a .pdb file directly from memory, use the [IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md) method.
63+
64+
## Example
65+
66+
```C++
67+
IDiaDataSource* pSource; // Previously created data source.
68+
DEFINE_GUID(expectedGUIDSignature,0x1234,0x5678,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08);
69+
DWORD expectedFileSignature = 0x12345678;
70+
DWORD expectedAge = 128;
71+
72+
HRESULT hr;
73+
hr = pSource->loadAndValidateDataFromPdb( L"yprog.pdb",
74+
&expectedGUIDSignature,
75+
expectedFileSignature,
76+
expectedAge);
77+
if (FAILED(hr))
78+
{
79+
// Report an error
80+
}
81+
82+
```
83+
84+
## See Also
85+
[IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)
86+
[IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md)
87+
[IDiaDataSource::loadDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md)
88+
[IDiaDataSource::loadDataFromIStream](../../debugger/debug-interface-access/idiadatasource-loaddatafromistream.md)

0 commit comments

Comments
 (0)