Thanks,
as current maintainer of itclng, I was just fixing a bug, which I had 
implemented myself ;-)  

It was not related to rivet, but there it was the first time the bug did show 
up with a segmentation violation.

Arnulf

Am Sonntag 02 Mai 2010 22:01:35 schrieb Karl Lehenbauer:
> That's awesome, Arnulf!  Congratulations…
> 
> On May 2, 2010, at 1:21 PM, Arnulf Wiedemann wrote:
> > Am Sonntag 02 Mai 2010 14:33:57 schrieb Arnulf Wiedemann:
> >> Hello,
> >> I have downloaded Apache 2.2.15 and Rivet 2.0.0 and installed them on my
> >> system (SUSE Linux 11.2)
> >>
> >> Thanks for finally releasing 2.0.0
> >>
> >> In general that works together. I am using Tcl 8.6b1.2 and Itcl 4.0b4
> >> cvs version.
> >>
> >> I can do a few statements including creating an itcl class and object
> >> and calling it, but when using a package with more classes and objects I
> >> get a segmentation violation. Calling the same package on the command
> >> line with tclsh8.6 makes no problems.
> >>
> >> Has anybody else the same problem and how can I debug apache with rivet?
> >>
> >> Best regards
> >> Arnulf Wiedemann (apw on tcl wiki)
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >
> > I could fix the problem myself after finding out the gdb httpd with: run
> > -X allows to debug apache.
> >
> > Problem was a bug in itclng package, which I could fix and now the
> > combination is working as expected.
> >
> > Arnulf
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to