Project

General

Profile

Actions
Copy link

Bug #1705

closed

shmat on x86_64 causes SIGSEGV in x11/gtk2

Added by davshao about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

To reproduce, on an x86_64 machine (tested on a Shuttle SG45H7 and an Intel Core
2 Duo Macbook 2.1), from a current DragonFly v2.5.1 1061.ge9fe2 X86_64_GENERIC
build, install modular xorg and gtk+-2.18.9 from current pkgsrc, and run
git-demo which SIGSEVs. No such SIGSEGV occurs on an i386 machine.

Attached is a gdb backtrace. Of interest are gtk2 GdkImage, in this case,
parameter image, a struct that has a field mem that is if shm is enabled on
x86_64 produces an

invalid address 0x8400000:      Cannot access memory at address 0x8400000

Actually image_info also has a field that points to a list static_image of
GdkImage's.

Files

gtk-demo_debug.txt (5.77 KB) gtk-demo_debug.txt davshao, 03/26/2010 06:15 PM
Actions
Copy link
 #1

Updated by Anonymous about 14 years ago

This simple test case succeeds in x86 but fails (segfaults) in amd64:

http://gitweb.dragonflybsd.org/~beket/pcca-tests.git/blob_plain/master:/sys/shm.h/t_shmat.c

Cheers

Actions
Copy link
 #2

Updated by dillon about 14 years ago

:Stathis Kamperis <> added the comment:
:
:This simple test case succeeds in x86 but fails (segfaults) in amd64:
:
:http://gitweb.dragonflybsd.org/~beket/pcca-tests.git/blob_plain/master:/sys/shm.h/t_shmat.c
:
:Cheers
:
:----------
:status: unread -> chatting

It just looks like a return value problem in kern/syscalls.master
   and in how the sysmg_result is set.  I'll get it fixed.
-Matt
                    Matthew Dillon 
                    &lt;&gt;
Actions
Copy link
 #3

Updated by alexh about 14 years ago

Commited in 65cac0a7e0f5b540e524e8872d616c4aa03ca6a8

Actions
Copy link

Also available in: Atom PDF