On Sun, 2011-05-15 at 23:57 +0200, Samuel Thibault wrote: > Svante Signell, le Sun 15 May 2011 23:52:10 +0200, a écrit : > > On Sun, 2011-05-15 at 23:34 +0200, Samuel Thibault wrote: > > > Svante Signell, le Sun 15 May 2011 23:20:52 +0200, a écrit : > > > > Segmentation fault > > > > > > Do you have a core file? Does your shell perhaps has limited core size > > > limit? (ulimit -a to check) > > > > Sorry I don't find any core file anywhere: > > ulimit -a > > socket buffer size (bytes, -b) unlimited > > core file size (blocks, -c) unlimited > > So it's unlimited, but you don't have a core file? What does > /servers/crash point to?
lrw-r--r-- 1 root root 10 Mar 18 16:05 /servers/crash -> crash-kill > > > The address is really bogus, use show registers to know where it comes > > > from, check eip, say 0x1234, use l * 0x1234 to know where that is, etc., > > > i.e. the usual "let's collect all trivial information before looking for > > > some direction". > > > > Sorry, I need more info here. > > Well, it doesn't really matter to understand much assembly. At worse > paste the result on the list. > > > I thought development was made with high-level languages nowadays (at > > least C-level) > > It is. But bugs are quite often when things go wrong ;) ?? > > Update on optimization levels: -O1 does not work either :( > > Other compiler switches are: -fno-strict-aliasing -fvisibility=hidden > > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wall > > There are a lot of warnings though: maybe some of them can cause > > problems. > > Possibly. > > It could be very worth trying to build with the exact same compiler and > libc on linux, to check whether it gets a crash too. I'll try that later. Report in due time.
