Re: [Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Schwab,Wilhelm K
oject@lists.gforge.inria.fr Subject: Re: [Pharo-project] FFI error message: Heisenbug On Sun, Mar 25, 2012 at 9:36 AM, Schwab,Wilhelm K mailto:bsch...@anest.ufl.edu>> wrote: I'm working on GSL+callbacks, and have hit a genuine Heisenbug - the behavior changes depending on when/where I b

Re: [Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Schwab,Wilhelm K
ro-project-boun...@lists.gforge.inria.fr] on behalf of Eliot Miranda [eliot.mira...@gmail.com] Sent: Sunday, March 25, 2012 3:35 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] FFI error message: Heisenbug On Sun, Mar 25, 2012 at 9:55 AM, Schwab,Wilhelm K mailto:bsch...@anest.ufl.edu>

Re: [Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Eliot Miranda
On Sun, Mar 25, 2012 at 9:36 AM, Schwab,Wilhelm K wrote: > I'm working on GSL+callbacks, and have hit a genuine Heisenbug - the > behavior changes depending on when/where I break and/or step over or into > code. Callbacks are getting hit successfully(!!!) but there is one > function that crashes

Re: [Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Eliot Miranda
inLibrary:'libgslWrapper.so' ? > Bill > > > -- > *From:* pharo-project-boun...@lists.gforge.inria.fr [ > pharo-project-boun...@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm > K [bsch...@anest.ufl.edu] > *Sent:* Sunday, March 2

Re: [Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Schwab,Wilhelm K
eed exported by the wrapper? Bill From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bsch...@anest.ufl.edu] Sent: Sunday, March 25, 2012 12:36 PM To: pharo-project@lists.gforge.inria.fr

[Pharo-project] FFI error message: Heisenbug

2012-03-25 Thread Schwab,Wilhelm K
I'm working on GSL+callbacks, and have hit a genuine Heisenbug - the behavior changes depending on when/where I break and/or step over or into code. Callbacks are getting hit successfully(!!!) but there is one function that crashes, unless I step over the call, in which case I get an error. In