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

[Wael Kdouh <waelkdouh@xxxxxxxxx>]

Greg when I tried to used gdb with simics the segmentation fault displayed the following:

Program received signal SIGSEGV, Segmentation fault.

[Switching to Thread 182910354336 (LWP 25927)]

0x0000002a9e435ca0 in ?? ()

(gdb) backtrace 3

#0  0x0000002a9e435ca0 in ?? ()

#1  0x0000002a9e320a33 in ?? ()

#2  0x0000000004dde670 in ?? ()

(More stack frames follow...)

As you can see there are no function names which makes it hard to trace. Let me know what you think.

On Tue, Aug 4, 2009 at 7:22 PM, Greg Byrd <gbyrd@xxxxxxxx> wrote:

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.
>

_______________________________________________
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.

--
Sincerely yours,

Wael Kdouh