|
If I knew what I was looking for. It's entirely possible that my debugging skills are lacking.
|
|
|
|
|
Apparently the fact that the serialization requires (as far as I can tell) the extra step of reading the count into a variable breaks the symmetry between save and load operations, so I have to overload them individually rather than handling both in a serialize() overload. This is what I've tried:
namespace boost
{
namespace serialization
{
template<class Archive>
void save(Archive&ar, const std::chrono::nanoseconds&time, const unsigned int version)
{
long long count{ time.count() };
ar&count;
}
template<class Archive>
void load(Archive&ar, std::chrono::nanoseconds&time, const unsigned int version)
{
long long count;
ar&count;
time = std::chrono::nanoseconds(count);
}
}
}
BOOST_SERIALIZATION_SPLIT_FREE(std::chrono::nanoseconds)
It seems to work, though I'm not confident that this is the way it's supposed to be done.
|
|
|
|
|
Vaguely years ago I recall being able to do this, but I'm having a senior moment.
I have a program, lets call it test.exe, that is launched by another program that starts as a service. Is there a way to configure VS2015 to launch and run test.exe in the debugger?
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Hi,
You are probably looking for the 'Image File Execution' registry key:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
If you want to avoid manually editing registry keys... you can download GFlags[^] to enable automatic debugger attachment. All it really does is set those registry keys for you.
Best Wishes,
-David Delaune
|
|
|
|
|
ooookay, I didn't expect that answer. Totally new to me, I'll look into it.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: ooookay, I didn't expect that answer.
Liquid Nitrogen. It's what I use for branding my cattle[^].
charlieg wrote: Totally new to me
I highly recommend learning how to use all of the debugging tools.
Best Wishes,
-David Delaune
|
|
|
|
|
Lol, just perused the gflags area. Might be a little heavy for what I need, but very interesting items.
Thanks
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: Might be a little heavy for what I need, but very interesting items.
Two thoughts:
1.) If you actually want to debug an error occuring when ProgramB is launched from ProgramA. There is no other way.
2.) If your question was worded incorrectly and you just simply need to debug ProgramB then just attach a debugger to it.
Best Wishes,
-David Delaune
|
|
|
|
|
Assuming that test.exe is a Debug version, or you have the source, you can just launch it directly from Visual Studio. But if it is not a Debug version you will not get much useful information from the debugger.
[edit]
Also you can attach the debugger to a running process.
[/edit]
|
|
|
|
|
I have the debug code, so this approach might work. I normally live in the embedded world, and the magic of attaching to running processes to debug is mostly a foreign concept.
I hope this works....
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
It helps to have all the source code also, and/or the .PDB file with the debug information, so you can see proper details of what is going on. Sounds complicated, but it's really useful.
|
|
|
|
|
Hi
I am getting a local variable overlayed now I am beginning to think it maybe because of the way I declared it
for example void process_trace()
{
char BASSM[2] = {0X0C, 0XEF};
This is still considered a local variable even though its assigned value since I didn't use the key word static
So I guess on entry to the function the complier re-initializes the value everytime
I guess I am thinking since this variable is some how being overlayed and I am not changing the value I should make it static
Thanks
|
|
|
|
|
Where is it getting overlayed?
|
|
|
|
|
I made a DATA breakpoint in Visual Studio and the overlay was some where deep in Windows in ntdll I did a Call Stack and it wasn't in the function that BASSM was declared
truth is at the very least since the value of BASSM is not being changed I should qualify it with a const to save compiler the trouble of initializing it every time
|
|
|
|
|
No, you should first find out where it is being overwritten and why. This error tells you that you have a bug in your code, so rather than try to hide it, you need to fix it. But without seeing more of your code it is difficult to guess what might be the cause.
|
|
|
|
|
I could post all the code in the function but I don't think that would help
I'll spend tonite trying to figure it and regardless I'll re-declare BASSM as const
that still shouldn't stop the bug as its still a local stack variable
thanks
|
|
|
|
|
ForNow wrote: I'll re-declare BASSM as const
Well, good luck, but you still have a bug in your code.
|
|
|
|
|
I’ll post it tommorow if I don’t get anywhere it is not clearly apperent as I never move anything into BASSM
Thanks
|
|
|
|
|
For clarification the value of BASSM is different at the end of the process_trace() method, than the initialized value?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
the first byte of the BASSM X'0C' gets overlayed not sure where I am going to have to step thru process_trace and check BASSM intermittently
Thanks
|
|
|
|
|
If it get overwritten consistently, stepping through the method is the way to go.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
|
Thanks 
|
|
|
|
|
There was a VFETCH macro which basically copied over data from the Mainframe emulated storage to your program the macro had a length however it would append a NULL (CString Style) at the end so even though I specified 4 bytes it put a null at the 5 th byte
The local storage the way it is laid out by the compiler is not the way it’s declared in the function so even though the area the VFETCH macro was using wasn’t declared after the BASSM the compiler laid it out that way and the VFETCH overlaid the 1st byte of BASSM
I fixed this problem but I also moved the BASSM to global storage by making it static
Thanks for all the help
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
