From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 10927] segmentation fault in NVUploadToScreen, called from exaPutImage
Date: Fri, 29 Jun 2007 00:45:01 -0700 (PDT) [thread overview]
Message-ID: <20070629075409.068462DC007@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-10927-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
http://bugs.freedesktop.org/show_bug.cgi?id=10927
skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Comment #6 from skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org 2007-06-29 00:44 PST -------
The original bug should be fixed in latest git.
However, the SIGABRT problem is a different bug (not sure if it's our fault or
not).
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-06-29 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 15:05 [Bug 10927] New: segmentation fault in NVUploadToScreen, called from exaPutImage bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-10927-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-06-10 18:41 ` [Bug 10927] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-06-10 20:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-06-10 22:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-06-10 22:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-06-10 22:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-06-29 7:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2007-07-01 10:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070629075409.068462DC007@annarchy.freedesktop.org \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.