On Tue, 2011-05-17 at 10:27 +0200, Svante Signell wrote:
Further info. I think the problem is with gcc-4.6 mis-compiling.
(Another issue is the memora acces problems in gdb: bothe present with
gcc-4.4 and gcc-4.6).
Building exim-4.75-3 with gcc-4.6 -O2 results in a segfault:
(even though the pack
On Tue, 2011-05-17 at 10:17 +0200, Svante Signell wrote:
Further info on the installed versions built with gcc-4.4 -O2:
ii exim4 4.76-1 metapackage to ease Exim
MTA (v4) installation
ii exim4-base4.76-1 support files for all Exim
MTA (v4) packa
On Tue, 2011-05-17 at 01:03 +0200, Thomas Schwinge wrote:
> > uschar *slash;
> > struct stat statbuf;
>
> if (filename == NULL)
> goto out;
>
...
> out:
> > *error = string_sprintf("%s does not exist", filename);
> > DEBUG(D_route) debug_printf("%s\n", *error);
> > return FILE_NOT_
Hallo!
On Tue, 17 May 2011 00:42:12 +0200, Svante Signell
wrote:
> On Tue, 2011-05-17 at 00:13 +0200, Thomas Schwinge wrote:
> > > static int rda_exists(uschar *filename, uschar **error)
> >
> > Please continue here: what is this function doing? (You didn't past that
> > one.) Does it make se
On Tue, 2011-05-17 at 00:13 +0200, Thomas Schwinge wrote:
> > Additionally: No breakpoints are possible to set. Looks like they are
> > not honoured due to the memory address problems above.
>
> Strange.
Same problem with a working version: -O0
No breakpoints possible!
Starting program: exim4-
Hallo!
On Mon, 16 May 2011 22:42:24 +0200, Svante Signell
wrote:
> On Mon, 2011-05-16 at 20:28 +0200, Thomas Schwinge wrote:
> > On Mon, 16 May 2011 18:17:38 +0200, Svante Signell
> > wrote:
> > > Thread 5 (Thread 1285.10):
> > > #0 0x018eff4c in ?? ()
> > > #1 0x018f0749 in ?? ()
> > > #2
On Mon, 2011-05-16 at 20:28 +0200, Thomas Schwinge wrote:
> Hallo!
>
> Se GDB decided to give some information at least... :-)
>
> On Mon, 16 May 2011 18:17:38 +0200, Svante Signell
> wrote:
> > gdb
> > ===
> > gdb build-tree/build-exim4-daemon-heavy/exim
> > (gdb) run -C exim4-4.76/test/eximt
Hallo!
Se GDB decided to give some information at least... :-)
On Mon, 16 May 2011 18:17:38 +0200, Svante Signell
wrote:
> gdb
> ===
> gdb build-tree/build-exim4-daemon-heavy/exim
> (gdb) run -C exim4-4.76/test/eximtest/exim4.conf -bV
> Cannot access memory at address 0x6465766d
> Cannot acces
Attached. Added .txt extension so evolution understands the filetype.
task1267->vm_statistics () = 0 {4096 221571 24842 72332 3972 15639362 0 632902
565492 60309468 5217731 6665313 6595451}
task1267->vm_region (134217728) = 0x3 ((os/kern) no space available)
task1267->vm_map (0 4096 0 0 (null)
Attached.
rpctrace_exim4_light
Description: Binary data
Some more info, complete rpctraces (attached in two separate mails) and
a gdb backtrace from exim4-daemon-heavy.
rpctrace
rpctrace build-tree/build-exim4-daemon-{light,heavy}/exim -C
exim4-4.76/test/eximtest/exim4.conf -bV > rpctrace_exim4_{light,heavy}
2>&1
gdb
===
gdb build-tree/buil
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 :
> > And with gdb the only output I get is (and no stack)
> > gdb build-tree/build-exim4-daemon-light/exim
> >
> > Cannot access memory at address 0x548d
> >
> > (I get thi
On Sun, 2011-05-15 at 23:57 +0200, Samuel Thibault wrote:
> > 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 warning
Hallo!
On Sun, 15 May 2011 23:57:00 +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
> > >
> >
Svante Signell, le Mon 16 May 2011 00:04:48 +0200, a écrit :
> > 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
Try to make it point to crash-dump-core
> > > > The address is really
On Sun, 2011-05-15 at 23:20 +0200, Svante Signell wrote:
> On Sun, 2011-05-15 at 16:45 +0200, Thomas Schwinge wrote:
>
> Yes, I can reproduce with:
> build-tree/build-exim4-daemon-light/exim
> -C /home/srs/DEBs/exim/exim4-4.76/test/eximtest/exim4.conf -bV
>
> Cannot access memory at address 0xff
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 ha
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
> > limi
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:
ulimi
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)
> srs@kvm-hurd:~/DEBs/exim/exim4-4.76$
>
> And with gdb the only output I get is (and no stack)
> gdb build-tree/b
On Sun, 2011-05-15 at 16:45 +0200, Thomas Schwinge wrote:
> From this, and your later email, I would guess (I have not looked at the
> source code) that debian/minimaltest is a shell script (test harness),
> and runs its tests against the Exim binary
> build-tree/build-exim4-daemon-light/exim, the
On Sun, 15 May 2011 11:28:55 +0200, Svante Signell
wrote:
> I was asked by tschwinge to take a look at the install problems of
> exim4.
Thanks!
> running minimal functionality test for binary
> build-tree/build-exim4-daemon-light/exim in
> directory /home/srs/DEBs/exim/exim4-4.76/test
> Exim ve
Svante Signell, le Sun 15 May 2011 15:27:31 +0200, a écrit :
> Well it is a little complicated: the tests are run by a script in
> debian/rules. Where and how to invoke gdb?
Find out how and what the script invokes.
> if id -u Debian-exim ; then \i
> echo Debian-exim user found, r
On Sun, 2011-05-15 at 13:01 +0200, Samuel Thibault wrote:
> Svante Signell, le Sun 15 May 2011 11:28:55 +0200, a écrit :
> > I was asked by tschwinge to take a look at the install problems of
> > exim4. For me it does not even build under kvm, it segfaults during
> > tests, see below:
>
> Then use
Svante Signell, le Sun 15 May 2011 11:28:55 +0200, a écrit :
> I was asked by tschwinge to take a look at the install problems of
> exim4. For me it does not even build under kvm, it segfaults during
> tests, see below:
Then use gdb to get a backtrace.
Samuel
25 matches
Mail list logo
