|
Thanks alot, very helpful hint!! 
|
|
|
|
|
I have seen issues with something that works fine in all Windows OS's except some machines running 2000 or XP. I'm using a WM_COPYDATA to send text between windows. When it fails, messages that should appear do not. It is extremely hard to narrow it down further than that.
Is anyone aware of any issues using this message on the newer OS's?
|
|
|
|
|
Does it fail consistently? Have you used Spy++ on the recipient window to see if it is receiving the message?
Perhaps the author of this article might have some knowledge of it failing.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Well, I've looked into it a bit further. It is actually recieving the message but the pointer to the data seems to be off be quite a bit (haven't counted the offset yet). I can see the start of my struct in the dump but it is preceeded by a bunch of "junk". I really don't know why. I have one long and 2 int's followed by a char[256]. The long, int's and string are all in there but not at the correct starting point.
Any ideas?
|
|
|
|
|
Dave_ wrote:
Any ideas?
Having not ever used that message before, I'm afraid not.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
I noticed someone else mentioned a similar issue in the article you linked to. No answer posted unfortunately.
|
|
|
|
|
It appears that the author has not been good about answering any of them. Bummer.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Hi,
I saw a thread where wm_copydata failed due to the nvidia tray-icon app.
MfG
|
|
|
|
|
Ok, but since Dave_ was the one asking the question, you might want to respond to him. 
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Help, please!
How to access a member in a base class from within an __asm block?
Suppose, we have:
struct s1
{
int a;
};
struct s2 : s1
{
int b;
};
struct s3
{
s2 c;
};
then:
__asm mov eax, [eax]s3.c.b // just fine
but
__asm mov eax, [eax]s3.c.a // ERROR
|
|
|
|
|
Use this instead:
__asm mov eax, [eax]s3.c.b.a
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Yes, this works! Why, however this doesn't:
struct s2 : POINT
{
int b;
};
struct s3
{
int c;
};
__asm mov eax, [eax]s3.c.b.x // 'x' : ambiguous member name in 'second operand'
'x' couldn't be a reserved name, could it??
Is there any way to clarify it to compiler except for defining an offset explicitly, like:
enum { s3s2x = offsetof(s3, s2.x) };
and then
__asm mov eax, [eax + s3s2x]
|
|
|
|
|
How are you expecting to get to 'b' or 'x' through struct s3 since struct s3 and struct s2 know nothing of each other?
__asm mov eax, [eax]s3.c.b.x
^ this dot makes no sense
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Sorry, of course:
struct s2 : POINT
{
int b;
};
struct s3
{
s2 c;
};
__asm mov [eax]s3.c.b.x // error
__asm mov [eax]s3.c.x // error also
And, unfortunately, if s2 has no data members,
that is
struct s2 : POINT
{
void foo();
};
then I wouldn't know how to access POINT::x at all as
__asm mov [eax]s3.c.x
results in error again...
|
|
|
|
|
See if this helps:
int xx = ss3.c.x;
__asm mov eax, [eax][xx]
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Well,
enum
{
s3cx = offsetof(s3, c.x)
};
__asm mov eax, [eax + s3cx]
is better as it requires no additional code, but the point was to access it from within an __asm block with no helpers...
Take a look at this:
struct POINT3
{
int x;
int y;
int z;
};
struct s2 : POINT3
{
int b;
};
struct s3
{
s2 c;
};
Now,
__asm mov eax, [eax]s3.c.b.z // works fine
but
__asm mov eax, [eax]s3.c.b.x // doesn't!!
That's why I asked if 'x' was reserved or smth...
However, if s2 is
struct s2 : POINT3
{
void foo();
};
then
__asm mov eax, [eax]s3.c.z // fails too...
Any suggestions will be greatly appreciated and thanks for your input!
|
|
|
|
|
jk61 wrote:
Now,
__asm mov eax, [eax]s3.c.b.z // works fine
Why this does not yield a compiler error is odd, as 'b' cannot be resolved into anything further as it is an int type. Does that make sense? When you have . and -> notation, it means that the object (i.e., structs and classes) can be broken down even further.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Yes, it would be odd if it was C++ code, but for inline asm it's sort of normal, I suppose.
You suggested that syntax yourself, right? It didn't even cross my mind to try to access 'x' through 'b'. Do you have a ms vc compiler there to try it out?
|
|
|
|
|
jk61 wrote:
You suggested that syntax yourself, right?
Indeed I did. Shame on me!
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
I give up... That strange access, while compiles ok, results, in fact, in wrong offsets... So, it doesn't work after all and I go with enums 
|
|
|
|
|
Hi,
I'm getting the following error whenever I try to build a 'debug' version of any application.
LINK : fatal error LNK1209 program database "C:\test\Debug\test.pdb" differs from previous link; relink or rebuild
Error executing link.exe.
I have tried re-building but it doesn't solve the problem. I even re-installed VC++ but that also didn't help. This is not specific to an application since it occurs even when i build a simple AppWizard application.
Any idea how to solve this problem would be greatly appreciated.
Thanks,
Mel
|
|
|
|
|
Does it happen every time? Can you manually delete the .pdb file and re-build?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
|
|
|
|
|
Yes, it happens every time and for any application.
Yes, I can delete the .pdb files, but rebuilding doesn't solve the problem.
First time i've experienced this kind of problem in my 5+ years of using VC++ 
-Mel
|
|
|
|
|
You did reapply the service packs for VS60, I take it...
Steve S
|
|
|
|
|
Yes, I just applied Service Pack 5....but still can't build debug configurations
-Mel
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
