Re: An idea for seg violations in CINT

From: Rene Brun (Rene.Brun@cern.ch)
Date: Thu Mar 02 2000 - 18:58:54 MET


Hi Damir,
I am afraid that your suggestion will not help much.
Most of the time, a seg violation appears when you use a null pointer
in your code. Could you send us a few examples of seg violation
that we can reproduce and for which having the scheme that you propose
would help ?

Rene Brun



Damir Buskulic wrote:
> 
> Hi,
> 
> I just had a thought about how to remove/prevent some of the seg
> violations in ROOT/CINT. This is maybe not at all possible but...
> I noticed that there are overloaded new and delete operators in ROOT. Is
> it a weird idea to have these functions maintaining a list of allocated
> memory, and CINT, when accessing a memory in interpreted mode, looking
> at this list to determine if the operation is legal or not.
> This would lead obviously to a slowdown of the whole operation of the
> interpreter but it could be a special "protected" mode.
> 
> what are the showstoppers ? Am i missing something obvious ?
> 
> Damir
> --
> =====================================================================
> | Damir Buskulic                  | Universite de Savoie/LAPP       |
> |                                 | Chemin de Bellevue, B.P. 110    |
> | Tel : +33 (0)450091600          | F-74941 Annecy-le-Vieux Cedex   |
> | e-mail: buskulic@lapp.in2p3.fr  | FRANCE                          |
> =====================================================================
> mailto:buskulic@lapp.in2p3.fr



This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:20 MET