what I am doing regarding Heap corruption
-
Since many have been so kind as to help me out i will spell out exactly what I am doing The Windows Program is a client to Z/os Mainframe program. I download a file (variable blocked) the output of a MainFrame Assembler program listing. This on the mainframe is called a sysadata file. The Windows exe calls the dll to basically convert the binary representation of the listing into readable format The routine I having the exception in is a subroutine called by another routine in the DLL The file i/o is done in the DLL. I think I am going to take out all the storage allocation out of the DLL is just causing me all sorts of problems the structure I'll pass from the exe to the dll will have the maximum amount of storage I need I do a number of STL objects such as maps in the DLL basically a number of map objects I have already generated them I hoping that when the exe needs the information from the DLL I dont have issues referencing them
-
Since many have been so kind as to help me out i will spell out exactly what I am doing The Windows Program is a client to Z/os Mainframe program. I download a file (variable blocked) the output of a MainFrame Assembler program listing. This on the mainframe is called a sysadata file. The Windows exe calls the dll to basically convert the binary representation of the listing into readable format The routine I having the exception in is a subroutine called by another routine in the DLL The file i/o is done in the DLL. I think I am going to take out all the storage allocation out of the DLL is just causing me all sorts of problems the structure I'll pass from the exe to the dll will have the maximum amount of storage I need I do a number of STL objects such as maps in the DLL basically a number of map objects I have already generated them I hoping that when the exe needs the information from the DLL I dont have issues referencing them
-
Quote:
The Windows exe calls the dll to basically convert the binary representation of the listing into readable format
A simple workaround would be moving that code inside the executable.
"In testa che avete, Signor di Ceprano?" -- Rigoletto
A little bit of a background I am basically a mainframe assembler language programmer I have worked for software vendor and IBM on their OS after 2000 I started getting layed off all over the place. it was it was suggested to me that I learn something new I started with C then Windows then MFC, along the way I got a Job with the US federal govt the IRS it is my day job Im on the east cost in NY. When It came to renew my IBM MainFrame yearly license and I inquired why the cost was higher than others they told me I have a right to sell the software I develop. I then started to focus my attention on that The z/os as a server and a Windows client Back to why I didnt make this code part of the .exe. The .DLL would be invoked by multiple user. Every user of the .exe would need to perform this functionality Again thank you for help I could never have gotten this far without the kindness of people like yourself
-
A little bit of a background I am basically a mainframe assembler language programmer I have worked for software vendor and IBM on their OS after 2000 I started getting layed off all over the place. it was it was suggested to me that I learn something new I started with C then Windows then MFC, along the way I got a Job with the US federal govt the IRS it is my day job Im on the east cost in NY. When It came to renew my IBM MainFrame yearly license and I inquired why the cost was higher than others they told me I have a right to sell the software I develop. I then started to focus my attention on that The z/os as a server and a Windows client Back to why I didnt make this code part of the .exe. The .DLL would be invoked by multiple user. Every user of the .exe would need to perform this functionality Again thank you for help I could never have gotten this far without the kindness of people like yourself
-
A little bit of a background I am basically a mainframe assembler language programmer I have worked for software vendor and IBM on their OS after 2000 I started getting layed off all over the place. it was it was suggested to me that I learn something new I started with C then Windows then MFC, along the way I got a Job with the US federal govt the IRS it is my day job Im on the east cost in NY. When It came to renew my IBM MainFrame yearly license and I inquired why the cost was higher than others they told me I have a right to sell the software I develop. I then started to focus my attention on that The z/os as a server and a Windows client Back to why I didnt make this code part of the .exe. The .DLL would be invoked by multiple user. Every user of the .exe would need to perform this functionality Again thank you for help I could never have gotten this far without the kindness of people like yourself
I don't know the details of your application, but in the PC/Windows world it's rare to have more than one user running on the same machine. Even if you have more than one user, each process (.exe program) has it's own separate memory space. Using a DLL instead of a single program to save memory makes little sense these days. I know some people might disagree with me, but this is a broad brush picture. Anyway it doesn't pay off in terms of complications it adds to your project, doubly so if you are a newcomer to this field. In short, my recommendation would be to give up on having a DLL and putting everything in a single program. If latter on, when the program is working well, you discover that using a DLL makes sense, you can change it. In the meantime you would have gained more familiarity with the OS/tools/programming language and it would be easier for you to transition. Just my $0.02
Mircea
-
I don't know the details of your application, but in the PC/Windows world it's rare to have more than one user running on the same machine. Even if you have more than one user, each process (.exe program) has it's own separate memory space. Using a DLL instead of a single program to save memory makes little sense these days. I know some people might disagree with me, but this is a broad brush picture. Anyway it doesn't pay off in terms of complications it adds to your project, doubly so if you are a newcomer to this field. In short, my recommendation would be to give up on having a DLL and putting everything in a single program. If latter on, when the program is working well, you discover that using a DLL makes sense, you can change it. In the meantime you would have gained more familiarity with the OS/tools/programming language and it would be easier for you to transition. Just my $0.02
Mircea
