#321: Hard lockup on Samsung NC20 on console switch
--------------------+-------------------------------------------------------
Reporter: TobiX | Owner: somebody
Type: defect | Status: new
Priority: major | Component: modesetting
Version: trunk | Resolution:
Keywords: | Blocking:
Blockedby: |
--------------------+-------------------------------------------------------
Comment(by kensmith):
I attempted to get gdb to give me a stack trace after
(gdb) handle SIGUSR1 nostop
When the crash happens, the GDB session becomes nonresponsive so I am not
able to get a backtrace. I believe the backtrace wast3 was able to get
must be the backtrace from the signal handler for SIGUSR1.
I'm fairly comfortable with GDB so I'm happy to help debug this issue.
Would someone please let me know where I can set some breakpoints to be
able to single step toward the likely point of the crash? I have zero
familiarity with openchrome or X internals.
--
Ticket URL: <http://www.openchrome.org/trac/ticket/321#comment:15>
openChrome <http://www.openchrome.org/>
The openChrome project
_______________________________________________
openchrome-users mailing list
[email protected]
http://wiki.openchrome.org/mailman/listinfo/openchrome-users
Main page:
http://www.openchrome.org
Wiki:
http://wiki.openchrome.org
User Forum:
http://wiki.openchrome.org/tikiwiki/tiki-view_forum.php?forumId=1
