[Mono-devel-list] Mono segfaults with updated kernel?? 2.6.10
vargaz at gmail.com
Thu Jan 20 07:59:03 EST 2005
Could you post the output of mono --version ?
On Wed, 19 Jan 2005 15:16:16 -0800, Joshua Rodman <jrodman at ducker.org> wrote:
> On Wed, Jan 19, 2005 at 10:55:52PM +0000, Paul wrote:
> > > It's possible I've made some kind of generic mistake with kernel
> > > updates, but mono is segfaulting with a built 2.6.10 kernel.
> > I'm using 18.104.22.168-1090_FC4 (rawhide FC) and have built mono from source
> > and on 4 different machines (all running the same kernel and under
> > rawhide) have not had it skip a beat.
> > Are you running Mono as rpms or from sources you've compiled yourself?
> > It shouldn't make much of a difference, but can.
> This is with the Ximian SuSE Linux Enterprise Server 9 RPMs for mono
> > > Wine segfaults also, but later, and I distrust wine
> > > as a canary due to its sentitive memory layout requirements.
> > Again, nerry a problem with Wine (or Crossover Office) on the kernels
> > I'm using.
> Wine being sensitive to memory layout is a well documented problem, and
> will crash with various security patches installed.
> Of course, I was not suggesting that mono fails for all, or even most
> users of 2.6.10, surely someone would have noticed before me. I would
> love suggestions of where to look, however, as hundreds of other
> binaries are all running without a hitch, and the production build is
> not very debugger friendly.
> For those who might be interested, attached is the output of strace32.
> It seems like the process is dying during initial load/link. This is
> running '/usr/bin/mono /usr/lib/mono/1.0/mcs.exe' with no arguments.
> Am I correct? Is my distribution broken?
More information about the Mono-devel-list