Hi Steve. What I sent is all I have. I don't have a perl built with debugging. I think I did turn on -g with the CtCmd module and tried to gdb the problem. Perhaps there is something here I can do to get information for you. I am not proficient in this area so some guidance will be necessary to get the details I think you are going to need. I did buy the perl modules book and have read it. But it was a ways over my head. But I assume that some small thing has changed in 5.10 that has caused the module to start failing where it has worked for all the 5.8 series. It have not seen problems in other scripts not using the CtCmd module so I would guess it is a module issue. Let me know what I can go to help. It is easily reproducable. > From: "Steve Peters via RT" <perlbug-followup@perl.org> > Reply-To: perlbug-followup@perl.org > RT-Ticket: perl #51238 > Managed-by: RT 3.6.HEAD (http://www.bestpractical.com/rt/) > RT-Originator: steve@fisharerojo.org > MIME-Version: 1.0 > Content-Type: text/plain; charset="utf-8" > Date: Thu, 05 Jun 2008 08:49:35 -0700 > > On Thu Feb 28 10:11:25 2008, warren.l.dodge@tektronix.com wrote: > > > > This is a bug report for perl from warren.l.dodge@tektronix.com, > > generated with the help of perlbug 1.36 running under perl 5.10.0. > > > > > > ----------------------------------------------------------------- > > [Please enter your report here] > > > > I am installing all new gnu tools and perl etc. I have gcc-4.2.3 and > > perl-5.10.0. In building the ClearCase::CtCmd moduke I get these > > errors > > when I do the make test > > > > *** glibc detected *** free(): invalid pointer: 0x553c6700 *** > > > > I wrapped the free call in CtCmd.xs with printf statements and it > > appears the error is outside of them. > > > > argv >>> > > argv <<< > > block_done >>> > > block_done <<< > > block_done >>> > > block_done <<< > > *** glibc detected *** free(): invalid pointer: 0x553c6700 *** > > > > I am not sure where the error is originating from the erro either. > > > > I haven't a clue as to how to debug this type of problem. Any help > > would > > be appreciated. > > > > > Do you have more of a backtrace? Most Linux versions usually will puke > out where there problems occured. > > >Thread Next