On 05/03/2012 04:22 PM, Michael Mol wrote:
>> It'd be interesting to understand why I'm getting the segfault with the
>> 295.40, but being a closed driver I suppose there is little I can diagnose.
> 
> Emerge with --ggdb3, enable core dumps (I forget the particular
> sysctl, sorry), and open up the core dump in gdb. At the very least,
> you might get something interesting if the segfault happens in a stack
> frame belonging to an open-source function a closed blob links to, or
> if the segfault happens in a pure portion of the stack.
> 
> (For example, on my broken boxes, the stack hadn't gotten into
> application-specific portions; it was still trying to get into the
> general CRT prologue code.)

X prints a backtrace when it segfaults and I saw some nvidia_* stuff I
*think* at the top of the stack. I'll re-check and possibly try your
suggestion.

raffaele

Reply via email to