[Info-vax] calloc fails with access violation

[VAXman- at SendSpamHere.ORG]

In article <92037288-d5bd-413a-ae5c-86c2d1e9ef05 at r42g2000yqj.googlegroups.com>, Jose Cuevas <jcuevas at mac.com> writes:
>{...snip...}
>PS I'll not be happy until I understand how the char * VS descriptor
>thing is messing with my calloc. The things that do not add-up yet
>are: i'm copying the contents of the cobol string to a c-string, I
>inspect the contents of the strings and all seems to be in order, from
>then on all I use is the string created in C. The address of the
>descriptor is the same as that of the char *, the only difference I
>see is that descriptor gives me a size, which is not an issue in my
>case. The ACCESSVIOL is raised at different places and never with the
>same record. (does tend to repeat somewhat with the same record but
>not in a consistent way). We have another C library that we use in
>Cobol with char * and never had problems with it for about 4 years
>now.

Perhaps you've just been lucky?  With coding like you've demonstated
in your prior post, you are looking to shoot yourself in the foot at
some time in the future... you've just not taken proper aim to date.

 
>I appreciate every ones help, will keep trying all of your suggestions.

Is there some reason why you will not post the stack dump?  Let's see
where and why you are getting an ACCVIO once and for all.  Speculation
has only managed to waste bandwidth with sage and salient programming
suggestions but we are all shooting blind-folded without seeing your
stack dump.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

  http://www.quirkfactory.com/popart/asskey/eqn2.png
  
  "Well my son, life is like a beanstalk, isn't it?"