kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #38249
Re: Segfault that just started happening
Hi,
On 31.10.2018 14:42, Strontium wrote:
>> The error was 'BadValue (integer parameter out of range for operation)'.
>> (Details: serial 8548 error_code 2 request_code 154 minor_code 24)
The segmentation fault happens because the error handler for X errors
tries to exit the program, and stumbles over invalid objects there. This
is an error path that is badly tested, because these errors are usually
difficult to reproduce, so I'd ignore the segmentation fault here and
focus on the X error.
The major request code (154) is dynamically allocated, so it is
difficult to tell which X extension caused it. The most likely candidate
is GLX, where minor opcode 24 is X_GLXCreateNewContext.
Do other OpenGL based programs work for you?
Does glxinfo report Direct Rendering to be active?
Simon
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References
-
5.1
From: Wayne Stambaugh, 2018-10-17
-
Re: 5.1
From: Maciej Sumiński, 2018-10-19
-
Re: 5.1
From: Maciej Suminski, 2018-10-21
-
Re: 5.1
From: Seth Hillbrand, 2018-10-22
-
Re: 5.1
From: Maciej Sumiński, 2018-10-23
-
Re: 5.1
From: Seth Hillbrand, 2018-10-23
-
Re: 5.1
From: Maciej Sumiński, 2018-10-23
-
Re: 5.1
From: Wayne Stambaugh, 2018-10-24
-
Re: 5.1
From: Maciej Suminski, 2018-10-24
-
Segfault that just started happening
From: Strontium, 2018-10-31