Re: Using malloc/Calloc under metal C
Thanks regarding debugging I see David Cole Created another niche > On Nov 6, 2019, at 11:25 AM, scott Ford wrote: > > I had to dig around for Metal C info ..so been there > >> On Wed, Nov 6, 2019 at 11:23 AM Joseph Reichman >> wrote: >> >> Thanks BTW the only way to debug this code is debug the generated >> assembler >> >> >> There is no debug tool support for this which really isn’t a big deal for >> me as getting zos explorer to work for AMODE 64 C code had proved to be a >> challenge of its own >> >> >> Thanks On Nov 6, 2019, at 11:16 AM, scott Ford wrote: >>> >>> Joe, >>> >>> Did you checkout this url ? >>> >>> https://www.metalc.guru/ >>> On Wed, Nov 6, 2019 at 10:04 AM Joseph Reichman wrote: Hi I am having all sorts of problems with LE in regards to XL C and >> thinking of switching to METAL C I have a DLL but in practical purposes that can be looked at as a bunch of C routines The routines work on storage accessed by the first function My question is under METAL C when you do a malloc / Calloc what is the life span of that storage Is it around after you leave the routine that allocated it Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >>> >>> -- >>> >>> >>> >>> *IDMWORKS * >>> >>> Scott Ford >>> >>> z/OS Dev. >>> >>> >>> >>> >>> “By elevating a friend or Collegue you elevate yourself, by demeaning a >>> friend or collegue you demean yourself” >>> >>> >>> >>> www.idmworks.com >>> >>> scott.f...@idmworks.com >>> >>> Blog: www.idmworks.com/blog >>> >>> >>> >>> >>> >>> *The information contained in this email message and any attachment may >> be >>> privileged, confidential, proprietary or otherwise protected from >>> disclosure. If the reader of this message is not the intended recipient, >>> you are hereby notified that any dissemination, distribution, copying or >>> use of this message and any attachment is strictly prohibited. If you >> have >>> received this message in error, please notify us immediately by replying >> to >>> the message and permanently delete it from your computer and destroy any >>> printout thereof.* >>> >>> -- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > > -- > > > > *IDMWORKS * > > Scott Ford > > z/OS Dev. > > > > > “By elevating a friend or Collegue you elevate yourself, by demeaning a > friend or collegue you demean yourself” > > > > www.idmworks.com > > scott.f...@idmworks.com > > Blog: www.idmworks.com/blog > > > > > > *The information contained in this email message and any attachment may be > privileged, confidential, proprietary or otherwise protected from > disclosure. If the reader of this message is not the intended recipient, > you are hereby notified that any dissemination, distribution, copying or > use of this message and any attachment is strictly prohibited. If you have > received this message in error, please notify us immediately by replying to > the message and permanently delete it from your computer and destroy any > printout thereof.* > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using malloc/Calloc under metal C
I had to dig around for Metal C info ..so been there On Wed, Nov 6, 2019 at 11:23 AM Joseph Reichman wrote: > Thanks BTW the only way to debug this code is debug the generated > assembler > > > There is no debug tool support for this which really isn’t a big deal for > me as getting zos explorer to work for AMODE 64 C code had proved to be a > challenge of its own > > > Thanks > > On Nov 6, 2019, at 11:16 AM, scott Ford wrote: > > > > Joe, > > > > Did you checkout this url ? > > > > https://www.metalc.guru/ > > > >> On Wed, Nov 6, 2019 at 10:04 AM Joseph Reichman > >> wrote: > >> > >> Hi > >> > >> I am having all sorts of problems with LE in regards to XL C and > thinking > >> of switching to METAL C > >> > >> I have a DLL but in practical purposes that can be looked at as a bunch > >> of C routines > >> > >> The routines work on storage accessed by the first function > >> > >> My question is under METAL C when you do a malloc / Calloc what is the > >> life span of that storage > >> > >> Is it around after you leave the routine that allocated it > >> > >> Thanks > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > > > > > -- > > > > > > > > *IDMWORKS * > > > > Scott Ford > > > > z/OS Dev. > > > > > > > > > > “By elevating a friend or Collegue you elevate yourself, by demeaning a > > friend or collegue you demean yourself” > > > > > > > > www.idmworks.com > > > > scott.f...@idmworks.com > > > > Blog: www.idmworks.com/blog > > > > > > > > > > > > *The information contained in this email message and any attachment may > be > > privileged, confidential, proprietary or otherwise protected from > > disclosure. If the reader of this message is not the intended recipient, > > you are hereby notified that any dissemination, distribution, copying or > > use of this message and any attachment is strictly prohibited. If you > have > > received this message in error, please notify us immediately by replying > to > > the message and permanently delete it from your computer and destroy any > > printout thereof.* > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- *IDMWORKS * Scott Ford z/OS Dev. “By elevating a friend or Collegue you elevate yourself, by demeaning a friend or collegue you demean yourself” www.idmworks.com scott.f...@idmworks.com Blog: www.idmworks.com/blog *The information contained in this email message and any attachment may be privileged, confidential, proprietary or otherwise protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using malloc/Calloc under metal C
Thanks BTW the only way to debug this code is debug the generated assembler There is no debug tool support for this which really isn’t a big deal for me as getting zos explorer to work for AMODE 64 C code had proved to be a challenge of its own Thanks > On Nov 6, 2019, at 11:16 AM, scott Ford wrote: > > Joe, > > Did you checkout this url ? > > https://www.metalc.guru/ > >> On Wed, Nov 6, 2019 at 10:04 AM Joseph Reichman >> wrote: >> >> Hi >> >> I am having all sorts of problems with LE in regards to XL C and thinking >> of switching to METAL C >> >> I have a DLL but in practical purposes that can be looked at as a bunch >> of C routines >> >> The routines work on storage accessed by the first function >> >> My question is under METAL C when you do a malloc / Calloc what is the >> life span of that storage >> >> Is it around after you leave the routine that allocated it >> >> Thanks >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > > -- > > > > *IDMWORKS * > > Scott Ford > > z/OS Dev. > > > > > “By elevating a friend or Collegue you elevate yourself, by demeaning a > friend or collegue you demean yourself” > > > > www.idmworks.com > > scott.f...@idmworks.com > > Blog: www.idmworks.com/blog > > > > > > *The information contained in this email message and any attachment may be > privileged, confidential, proprietary or otherwise protected from > disclosure. If the reader of this message is not the intended recipient, > you are hereby notified that any dissemination, distribution, copying or > use of this message and any attachment is strictly prohibited. If you have > received this message in error, please notify us immediately by replying to > the message and permanently delete it from your computer and destroy any > printout thereof.* > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Using malloc/Calloc under metal C
Joe, Did you checkout this url ? https://www.metalc.guru/ On Wed, Nov 6, 2019 at 10:04 AM Joseph Reichman wrote: > Hi > > I am having all sorts of problems with LE in regards to XL C and thinking > of switching to METAL C > > I have a DLL but in practical purposes that can be looked at as a bunch > of C routines > > The routines work on storage accessed by the first function > > My question is under METAL C when you do a malloc / Calloc what is the > life span of that storage > > Is it around after you leave the routine that allocated it > > Thanks > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- *IDMWORKS * Scott Ford z/OS Dev. “By elevating a friend or Collegue you elevate yourself, by demeaning a friend or collegue you demean yourself” www.idmworks.com scott.f...@idmworks.com Blog: www.idmworks.com/blog *The information contained in this email message and any attachment may be privileged, confidential, proprietary or otherwise protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Using malloc/Calloc under metal C
Hi I am having all sorts of problems with LE in regards to XL C and thinking of switching to METAL C I have a DLL but in practical purposes that can be looked at as a bunch of C routines The routines work on storage accessed by the first function My question is under METAL C when you do a malloc / Calloc what is the life span of that storage Is it around after you leave the routine that allocated it Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
