Hello Angus,

Monday, November 24, 2008, 8:36:02 PM, you wrote:

   cgicc library has built in debug facilities. Turn them on to see
   what happens. It cannot crash at begin. It might crash
   at Cgicc constructor though. At the time cgi object is constructed
   all the form data is processed. If it crashes at begin then it is most
   probably some linkage problem.
  
   You can all so save form data that crashes cgicc and then load it
   and find out the problem.

A> I have this problem where as soon as I call begin() on the array returned by
A> getElements() I register a segmentation fault. Here's my code:
A> int main(int argc, const char *argv[]) {
A>         int nReturn = EXIT_FAILURE;
A>         try {
A>                 {
A>                         Cgicc cgi;
A>                         for(const_form_iterator iter = cgi.getElements().begin(); iter !=
A> cgi.getElements().end(); ++iter) {

A> and that's all there is to it. Valgrind registers a bunch of "conditional
A> jump or move depends on uninitialized values"s and then finally an "invalid
A> read". I've got what appears to be the latest cgicc (3.2.7). What am I doing
A> wrong?



--
Best regards,
Igor                            mailto:sprog@onli...



_______________________________________________
help-cgicc mailing list
help-cgicc@gnu....
http://lists.gnu.org/mailman/listinfo/help-cgicc