[Lazarus] Lazarus on POWER9 Little Endian

[Marc Weustink]

When debugging these kinds of X related errors, start your application with the (gtk) X option in synchronized mode.
I can't remember which option it was, but Google will tell

Marc

On August 20, 2019 1:06:35 PM GMT+02:00, Tobias Giesen via lazarus <lazarus at lists.lazarus-ide.org> wrote:
>It seems to work slightly better on Fedora. It doesn't cause a signal
>and
>very briefly, an empty small window appears. The console output is like
>this:
>[tobias at blackbird lazarus]$ ./startlazarus
> is a file
>
>(startlazarus:3893): Gdk-ERROR **: 13:02:08.997: The program
>'startlazarus'
>received an X Window System error.
>This probably reflects a bug in the program.
>The error was 'BadValue (integer parameter out of range for
>operation)'.
>  (Details: serial 334 error_code 2 request_code 130 minor_code 3)
>  (Note to programmers: normally, X errors are reported asynchronously;
>   that is, you will receive the error a while after causing it.
>   To debug your program, run it with the --sync command line
>   option to change this behavior. You can then get a meaningful
>backtrace from your debugger if you break on the gdk_x_error()
>function.)
>Trace/breakpoint trap (core dumped)
>
>On Mon, Aug 19, 2019 at 9:24 PM Florian Klaempfl via lazarus <
>lazarus at lists.lazarus-ide.org> wrote:
>
>> Am 18.08.2019 um 11:41 schrieb Tobias Giesen via lazarus:
>> > Hello,
>> > I am trying to use Lazarus on a ppc64el processor under Ubuntu.
>> >
>> > Unfortunately startlazarus and lazarus crash with a segmentation
>fault in
>> > a call to XGetWindowProperty in gtk2widgetset.inc in function
>> > TGtk2WidgetSet.GetWindowManager.
>>
>> A stack trace and assembler dump at the crash location might be
>helpful ...
>> --
>> _______________________________________________
>> lazarus mailing list
>> lazarus at lists.lazarus-ide.org
>> https://lists.lazarus-ide.org/listinfo/lazarus
>>