Re: [Open Babel] Problem with gcc5 and above

2017-04-28 Thread Nicolas Cheron
Yes, it was on the same machine (stack was 8192kb) 2017-04-27 17:24 GMT+02:00 Noel O'Boyle : > Nice digging down. I presume that this was on the same machine? > > It could be something to do with changes in string handling (in the > compiler), particularly if you are a fan of flags for recent > s

Re: [Open Babel] Problem with gcc5 and above

2017-04-27 Thread Dmitri Maziuk
On 4/27/2017 10:24 AM, Noel O'Boyle wrote: > ... we don't want > to trade off too much speed for the common case (e.g. by allocating > everything on the heap), but it's good to keep an eye on it. I very much doubt the speed difference for the common case will be noticeable to the user, or even i

Re: [Open Babel] Problem with gcc5 and above

2017-04-27 Thread Noel O'Boyle
Nice digging down. I presume that this was on the same machine? It could be something to do with changes in string handling (in the compiler), particularly if you are a fan of flags for recent standards. We should definitely try to streamline our handling of large molecules though, and we should

Re: [Open Babel] Problem with gcc5 and above

2017-04-27 Thread Geoffrey Hutchison
>> If there is a way, in future versions, to change the stack >> limit in OpenBabel, I think it could be useful. > > Not really, even if there was a way: someone'll just try to load a > larger structure and hit the same thing again. Moreover, it's a type of denial of service attack on the underl

Re: [Open Babel] Problem with gcc5 and above

2017-04-26 Thread Dmitri Maziuk
On 4/26/2017 12:49 PM, Nicolas Cheron wrote: > If there is a way, in future versions, to change the stack > limit in OpenBabel, I think it could be useful. Not really, even if there was a way: someone'll just try to load a larger structure and hit the same thing again. Dima --

Re: [Open Babel] Problem with gcc5 and above

2017-04-26 Thread Nicolas Cheron
After digging a little bit, I found the cause of the problem, and it is not (directly) linked to OpenBabel. I have found that a code as simple as: #include using namespace std; int main(int nbarg, char * argv[]) { string List[40]; return 0; } can compile with g++5.4 but returns a segme

Re: [Open Babel] Problem with gcc5 and above

2017-04-22 Thread Noel O'Boyle
No known problems. Could you file a bug? On 22 Apr 2017 1:51 p.m., "Nicolas Cheron" wrote: > Dear all, > > I have a code in C++ that uses the OpenBabel library. Everything is > working smoothly with gcc4.8 or 4.9 (used to compile both OpenBabel and my > code). However, when I am using gcc5 and a

[Open Babel] Problem with gcc5 and above

2017-04-22 Thread Nicolas Cheron
Dear all, I have a code in C++ that uses the OpenBabel library. Everything is working smoothly with gcc4.8 or 4.9 (used to compile both OpenBabel and my code). However, when I am using gcc5 and above (I tried 5.4 and 6.3) I found some problems. For example, one of them seemed to be that I can not