gdb using Windows paths in dlopen()ed modules?
Wed Apr 13 02:17:00 GMT 2016
On 2016-04-12 10:20, Marco Atzeri wrote:
> On 22/02/2016 10:00, Yaakov Selkowitz wrote:
>> The following packages have been uploaded to the Cygwin distribution:
>> * mesa-11.0.9-2
>> * dri-drivers-11.0.9-2
>> * libglapi0-11.0.9-2
>> * libGL1-11.0.9-2
>> * libGL-devel-11.0.9-2
>> * libOSMesa8-11.0.9-2
>> * libOSMesa-devel-11.0.9-2
>> * libEGL1-11.0.9-2
>> * libEGL-devel-11.0.9-2
>> * libGLESv2_2-11.0.9-2
>> * libGLESv2-devel-11.0.9-2
>> * windowsdriproto-11.0.9-2
>> Mesa is an open-source implementation of the OpenGL specification, a
>> for rendering interactive 3D graphics.
>> Complete documentation on OpenGL usage and configuration can be found
>> This release has been rebuilt for LLVM 3.7.
> Hi Yaakov,
> we found a case where the 32bit is segfaulting
> while dri-drivers-11.0.9-1
> works fine.
> For reference:
> To replicate with octave is enough :
> run from xterm
> as dri-drivers seems absent from mesa-debuginfo
> I can not provide you a meaningful backtrace:
> #0 0xfc6d00a0 in ?? ()
> #1 0x43934357 in gallium_dri!__driDriverGetExtensions_swrast ()
> from E:/cygwin/lib/dri/swrast_dri.so
> #14 0x4fc1ae48 in glutJoystickGetCenter () from /usr/bin/cygglut-3.dll
I'm seeing this as well. Any idea why gdb is using with dlopen()ed
modules? This is preventing it from finding the split debuginfo.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin