Search:

grumpy: Thank you for taking your precious time and explaining this to me in such detail. I understand this matter perfectly now.

When I multiply the numbers 11-19 (that is 11*12...*18*19), Pelles C gives me the wrong answer. But when I add it bit by bit, until I added as much as the multiplication would do, I get the right...

Unicode, though I think I found a way to get the name through the handle on msdn (link).

I assume that approach could be used by passing the dll-handle, can't blame them for making it easy on...

Current stand: I can, thanks to your guidance change the access and set a memory breakpoint, using the LOAD_DLL_DEBUG_EVENT exception to get a valid address space. However, I can't seem to get the...

_Mike: Thanks, appreciated! Sorry for delayed response, been busy at my work. But I re-read the docs on debugging structures at MSDN and got a lot of ideas at least. Going to find out if they work...

The pointer will receive the old protection constant as I understand it, here is what the docs say:



Hmm, you seem to be on to something here. Just to clear things out:

1. GetProcAddress -...

Very strange indeed...

I was thinking you might have another value for Protect since you got another error code.

Ah, thanks, that explains the size of the region. Well, I read MSDN docs once...

LoadLibrary: I get the exact same results as before. another strange thing is that you get 487 while I get 998. Which constant are you using as mbi.Protect?

One more thing, if you look at my post...

But how come I get an address when asking for it? Shouldn't I get only zeroes then? I wrote another test class which just had a function called "sum" besides "main". Then I tried to get the address...

Well, any ideas? I re-write the troubling functions just to make it easier for aiders to read the code fast/easy :)

tabstop: I see, here it is then: VirtualProtectEx fails, throws different error codes for different memory protection constants

Hi,

I have a question but I already asked it on msdn. Though I find this forum better at answering and since I'm new I didn't know there was a windows session here too. Now that I found it, would...

Hi,

I'm moving to Pelles C after reading reviews about it here and elsewhere. I used MinGW previously and when I try compile my code with Pelles my code breaks.

There are a series of errors so...

talstop: You're right about that. I think, at some point I tried to compile it without parentheses and when it worked I just skipped them without thinking about how it might impact the rest. I...

tabstop: Strange, In my book it said they are equivalent. And I do get the same answers, would you mind telling me the difference?

However, when I use list[count] or list[i] the program crashes...

I want to be able to extend an array at run-time. Meaning that if it would have 10 fields I'd like to extend it to 20, then 30, and so on...

Here is another piece when I try to do this. This...

So, it seems the other options are the only ones, right? I mean the linked list or using realloc?

laserlight:

Sorry, I assumed it was obvious, my fault. But let me clear it out then:

I wonder why the the second part of the output looks at it does? I'm trying to extend an array by using a...

The code:

#include <stdio.h>
main () {
int size = 5;
int *pointer;
int list[size];
int count = 0;
pointer = list;

tabstop: You're the man! :)

Still not sure why it reacts on *, it not listed in either cmd as a command nor the msdn-link :(

Yeah, the later, atoi, that is why I got the wrong output according to what should be shown (a list of files). Read the other posts, I corrected them and gave you the cred for that path of the...

You're right. My fault. Sorry again :(

Ah, running cmd /? and then pressing enter a couple of times lead me to a text telling me some characters needed to be within "" when printed to console. & was among them, * was not, but ' was so I...

When I have two files that match, it pick the first one in alphabetic order. But what I wonder is, why wont I just get my character as it is? Is * threatened differently, as a way to communicate with...