Re: known way to reproduce an X.org segmentation fault

2019-03-01 Thread Stuart Henderson
On 2019-03-01, Mihai Popescu wrote: >> If you have a checkout of /usr/xenocara ... > > I have the cvsweb. I got the .core file with those instructions, run > gdb with my current X. I am not sure if snapshots X is compiled with > or without debug symbols. > Looking at some functions headers, I

Re: known way to reproduce an X.org segmentation fault

2019-02-28 Thread Mihai Popescu
> If you have a checkout of /usr/xenocara ... I have the cvsweb. I got the .core file with those instructions, run gdb with my current X. I am not sure if snapshots X is compiled with or without debug symbols. Looking at some functions headers, I think I should mention that in firefox the web

Re: known way to reproduce an X.org segmentation fault

2019-02-28 Thread Stuart Henderson
On 2019-02-28, dmitry.sensei wrote: > The community for some reason does not like problems with X and DRM :) > > ср, 27 февр. 2019 г. в 20:06, Mihai Popescu : > >> I tried again this link with a recent snapshot and the result is the >> same, X got a segfault. >> >> Is there a special debug run

Re: known way to reproduce an X.org segmentation fault

2019-02-27 Thread dmitry.sensei
The community for some reason does not like problems with X and DRM :) ср, 27 февр. 2019 г. в 20:06, Mihai Popescu : > I tried again this link with a recent snapshot and the result is the > same, X got a segfault. > > Is there a special debug run for X to be able to get some detailed >

Re: known way to reproduce an X.org segmentation fault

2019-02-27 Thread Mihai Popescu
I tried again this link with a recent snapshot and the result is the same, X got a segfault. Is there a special debug run for X to be able to get some detailed information, please? Does it worth to pursue this debug? Thanks.

Re: known way to reproduce an X.org segmentation fault

2019-02-15 Thread dmitry.sensei
Check your /etc/hosts пт, 15 февр. 2019 г., 14:54 Mihai Popescu mih...@gmail.com: > I installed firefox too, there is no problem with that page, I mean > X.org is not doing segmentation fault. It looks like chromium is > trying to do something nasty against X.org's stuff. > >

Re: known way to reproduce an X.org segmentation fault

2019-02-15 Thread Mihai Popescu
I installed firefox too, there is no problem with that page, I mean X.org is not doing segmentation fault. It looks like chromium is trying to do something nasty against X.org's stuff.

Re: known way to reproduce an X.org segmentation fault

2019-02-15 Thread Mihai Popescu
Got some details about this: X.org crashes only when I move the mouse pointer inside the big picture presented on the web page, the product itself. I captured the chomium output too: [49853:80110072:0215/111903.592670:ERROR:process_metrics_openbsd.cc(126)] Not implemented reached in bool