Zeoslib Portal

HI Jan, No worries. I'm not sure what you mean about it not being used by oracle functions, but those variables are used all the time for result sets as I showed in my sample console mode program on the first post of this. In 64bit mode with $A8 alignment (the default) that calculation will show 52 ...

HI Jan, No worries. I'm not sure what you mean about it not being used by oracle functions, but those variables are used all the time for result sets as I showed in my sample console mode program on the first post of this. In 64bit mode with $A8 alignment (the default) that calculation will show 52 ...

If there's something that needs to be looked at related to this (and it's one of the drivers I use), I'll be happy to take a look. Perhaps it should be a new thread since it's not related to the bug I noted.

-Mark

Note: This configuration might require you to clean up some of your code according to 64-bit rules..." https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Support_high-entropy_64-bit_ASLR Michal Could you expand on the "note" part of this? I'd love to know what clean-up you're re...

You are both correct. The memory error I reported is just a simple instance of record alignment. It's not mysterious in any way and a simple sizeof shows the difference in memory sizes. ASLR (or topdown memory allocation as I mentioned in that thread) can help to point out issues where pointers (or ...

We seem to have gone a bit afield from my post about this record alignment memory allocation bug. Note that this ASLR stuff doesn't relate to that particular issue. If there are problems in Zeoslib that are "solved" by turning off ASLR, then there are probably pointers that are being cast ...

If we find a bug we should report it, though in this specific case I'm not sure it's a bug in anything but the code I mentioned above. I could easily be wrong about this, but I'm not sure it's ever been a good idea to calculate the size of a record using the individual sizes of the datatypes. The or...

I can verify that what I fixed was an actual memory overrun (you can tell because the struct wasn't "zeroed" all the way to the end. If you have a small app that shows the UTF-16 charset issue I can take a quick look. Note that Zeos doesn't support the OCI_UTF16 connection mode setting (wh...

Note that this change only fixes the one issue I mentioned in my first post in this thread. I'm not suggesting it fixes anything beyond that. If there are other areas that are affected by memory allocations that are done in this same manner, they should be looked at for similar issues.

-Mark

I found out what's causing this particular heap issue. In AllocateOracleSQLVars it dynamically allocates memory for the TZSQLVars record, but I think it's assuming that the record is packed and so the allocation doesn't take into account the record field alignment setting (which defaults to Quad wor...

Hi all. I use FastMM5's debug mode to check my programs for heap corruption and memory leaks. When I run any queries using the Oracle protocol in 64bit while using FastMM_EnterDebugMode I get a "Memory Corruption Detected" error. Here's the info on the error and the simple console mode pro...

I vote yes! I use a very similar version and it has always worked well. Mine also checks
But maybe that's not needed.

@aehimself: Enjoy your vacation! This only caused non-unique indexes to be reported incorrectly, so I don't think it's any kind of major issue really, but good to get it fixed so thanks all. I really only use the getindexinfo call for informational display, not really for any major program logic (un...

Thanks Jan. The fixes for StrToBoolEx look good. Sorry about doing this as a user patch instead of a pr though github, but I changed machines recently and I'm still working on getting things setup. Now that that fix is in the reversed NON_UNIQUE flags for MySQL's GetIndexInfo should become more obvi...

The real world test is to call GetIndexInfo on a MySQL table that contains both a primary key and also a non-unique index. You should see the NON-UNIQUE column for the non-unique index = false (which is incorrect.) The only guess I can think of for your Meta.GetIndexInfo calls to work correctly is t...