The bug could be anywhere - your project code, on even in our libc code for example.
In general once SAFE_HEAP shows you a failure, you can look at that variable and try to see why it contains a wrong value. You can then add more SAFE_HEAP logging manually - for example if a global variable contains a bad value, you can add a printout in SAFE_HEAP_STORE, so that it prints out a stack trace when it writes to that location. That lets you find who wrote to it, and continue debugging from there. - Alon On Fri, Feb 28, 2014 at 2:36 PM, wolfviking0 <[email protected]> wrote: > Hi Alon, > > I am a little lost with the this bug : > > First it's append on some sample and sometime if I refresh the webpage > it's working. > Second if I disable FASTCOMP it's working too. > Third the code failed at the beginning of the execution with the first > call. > > Sorry but not sure to understand the 'due to a bug'. That means these > samples could be have a bug who are failing with fast comp ?? > > If it's a trouble about writing a memory address how I can catch that ? > > Tony > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
