Hi Todd,

> I have been using Bigloo 4.1a until this week. I am trying to use existing 
> code and build it with Bigloo 4.3a
> 
> 
> I am seeing an issue where a global variable is being over written when a 
> loadq is used to load a file that defines new functions. I added print 
> statements to print the global variable value. The over writing doesn't 
> happen at the same spot when run repeatedly from command line. When run as an 
> argument to valgrind, the spot where the variable is over written seems 
> consistent. I don't see anything remarkable in valgrind output or with the 
> functions being defined.
>
> Can you recommend any steps to narrow down what might be happening here?
If you can provide me with an actual example, I will be glad to have a
look at it. As is, I don't totally understand the problem you are
describing.

If you don't want your code to be public, we can discuss that privately.

> First I am going to try 4.2c and earlier to see where the issue may have been 
> introduced.
I would definitively recommend to directly switch to bigloo4.3b. I'm actively
working on that version that will be officially announce pretty soon.

> Thanks,
> 
> Todd D.

> I also had a couple of other issues that I was able to work around:
> 
>  1. bigloo.h could not be used as include to a C++ file. There was a brace 
> mismatch. I was able to restructure my code to make this a c file so this is 
> not an issue for me, but I thought you might want to know. I will try to 
> create an example if you are interested.
What do you mean. The C++ parts of bigloo.h file are incorrect? I will double
check that.

>  2. I was hiding load and loadq from the interpreter, so I had a module that 
> called the original load, loadq from a new name. importing this module causes 
> a segfault. I have removed the hiding functionality for now, but I would like 
> to pursue this. I will make an example and email that seperately.
I will try to re-construct something similar to what you are describing but
a concrete code would help for that too.

Thanks in advance,

-- 
Manuel

Reply via email to