Re: [Gems-users] Opal0.init Segmentation fault when enabling Wattch

[Greg Byrd <gbyrd@xxxxxxxx>]

Can you run within gdb -- or attach gdb to the process after it crashes?  You may be able to figure out where the segfault occurs.  I doubt anyone will be able to debug this without more information.

...Greg


Wael Kdouh wrote:
> When I enable the Wattch flag by setting it to 1(default 0) within 
> opal's configuration file I get the following error within simics when 
> execute the opal0.init command:
> Segmentation fault (SIGSEGV) in main thread
> The simulation state has been corrupted. Simulation cannot continue.
> Please restart Simics.
>
>
> This problem has been discussed before, but no solution was provided. 
> Any insight would be appreciated. 
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
> Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.