[cairo-bugs] [Bug 63461] [Patch] Segmentation fault when accessing xlib backend from different endian systems

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Nov 4 10:56:46 PST 2015


--- Comment #5 from irwin at princeton.edu <irwin at princeton.edu> ---
I tried the most-recent proposed patch
( https://bugs.freedesktop.org/attachment.cgi?id=106473 
and https://bugs.freedesktop.org/attachment.cgi?id=106474 )

In cairo 1.12.18:

I can confirm that the patch is fixing a similar crash 
on Solaris 9 SPARC and Solaris 10 SPARC when logging in from 
a x86_64 client (Apple OS X) over ssh.

But the patch introduces a new failure on Solaris 10 SPARC
when logging in from a Solaris 10 SPARC client over ssh:

a) Sometimes it works fine.  

b) Other times the appplication renders its windows and menus
lacking all text and icons.  
The application crashes (leaving no core dump) within a few operations.

c) Other times the application exits before anything is displayed.
Output is:
ssh -X -f  foo.example.com wireshark
Authenticated to  foo.example.com ([]:22).
The program 'wireshark' 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 144 error_code 2 request_code 131 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.)
Transferred: sent 15244, received 38328 bytes, in 1.8 seconds
Bytes per second: sent 8400.2, received 21120.6

d) Other times are identical to (c), but before crashing,
the app begins to display its splash screen.  The crash happens before
any text or icons are successfully displayed on the splash screen.

Retries produce results among a, b, c, or d with no apparent pattern.
So enough retries in launching the app will eventually hit (a) and be
usable, working around the issue.

You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cairographics.org/archives/cairo-bugs/attachments/20151104/403799ba/attachment.html>

More information about the cairo-bugs mailing list