Size of buffer passed to f_FUNCTION?
- Thread starter vefatica
- Start date
- May
- 12,623
- 152
In my tests associated with this question, using LPWSTR psz as argument to f_FUNCTION, TCC did not catch my writing beyond the end of the buffer pointed to by psz (and TCC crashed). Should it have caught such an error?
Charles Dye
Super Moderator
- May
- 4,846
- 116
Staff member
I seem to recall this value changing from one version to another.... Even if you know for sure that it's 16K in the current release, it may well be smaller in older versions.
rconn
Administrator
- May
- 12,827
- 180
Staff member
I have no idea what you're asking about -- what is "f_FUNCTION"?
If you're asking about the size of the buffer passed to a plugin function or command, it's 32K bytes (and always has been), regardless of whether it's a function or command.
TCC itself has no limits on string sizes, but I can't change it in the plugin calls without breaking every plugin in existence.
And no, TCC can't do anything about an ill-behaved plugin writing beyond the end of memory. There is no automagical way to uncorrupt a heap.
(And TCC didn't crash, your plugin did. If you neglected to include exception handling, you could take the TCC process down as well.)
Last edited:
