Hi,
I have created workspace file for windbg:10.0.10240.9 AMD64 version. My debug connection to target PC is over NETWORK cable.
Most of the details are persisted in workspace except for connection mode and breakpoints. Each time I have to give details of NET key and port and also set breakpoints.
How can this be avoided? This is annoying.
Batch files can be used launch windbg with arguments. Typicly it may contain
start “” /D "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64" /B
“windbg.exe” -k net:port=50000,key=1.2.3.4 -QY
On Tue, Aug 23, 2016 at 8:00 AM, <srinivaskumar.r> wrote:
> Hi,
>
> I have created workspace file for windbg:10.0.10240.9 AMD64 version. My
> debug connection to target PC is over NETWORK cable.
>
> Most of the details are persisted in workspace except for connection mode
> and breakpoints. Each time I have to give details of NET key and port and
> also set breakpoints.
>
> How can this be avoided? This is annoying.
>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></srinivaskumar.r>
set bu breakpoints they are saved in workspaces
breakpoints set with mouse clicks , addresses etc (aslr can corrupt )
are not saved
for repeaated connections with same parameters create a bat file with
"path to windbg.exe " -k net:port=xxxxx,key=iii.jjjj.kkkk.lllll
On 8/23/16, Menachem Shapira wrote:
> Batch files can be used launch windbg with arguments. Typicly it may
> contain
>
> start “” /D "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64" /B
> “windbg.exe” -k net:port=50000,key=1.2.3.4 -QY
>
>
>
>
> On Tue, Aug 23, 2016 at 8:00 AM, <srinivaskumar.r> wrote:
>
>> Hi,
>>
>> I have created workspace file for windbg:10.0.10240.9 AMD64 version. My
>> debug connection to target PC is over NETWORK cable.
>>
>> Most of the details are persisted in workspace except for connection mode
>> and breakpoints. Each time I have to give details of NET key and port and
>> also set breakpoints.
>>
>> How can this be avoided? This is annoying.
>>
>>
>> —
>> WINDBG is sponsored by OSR
>>
>> OSR is hiring!! Info at http://www.osr.com/careers
>>
>>
>> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
>> software drivers!
>> Details at http:
>>
>> To unsubscribe, visit the List Server section of OSR Online at <
>> http://www.osronline.com/page.cfm?name=ListServer>
>>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
> drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at
> http:</http:></http:></http:></srinivaskumar.r>