begin Sean Neakums quotation: In Emacs' case, there's a niggle with this: if there's already an emacs-21.1.1 file there, it'll dump as emacs-21.1.2, and the dumped file will have that version embedde
A lot of binaries have generated strings put into them which are created, an example would be: cpp -E << /EOF __TIME__ /EOF "12:25:35" Compilers can also put strings into .o files which include the t
begin Sean Neakums quotation: I think I can finally reproduce the bogus dumps. I just did it here, three times. What I did was: run the io-test program above on two different files for approx three m
Can you expand on the 'dumps' I am not really familiar with the emacs build process, so I don't know which part of the process you are refering to here. Steve -- Steve Lord voice: +1-651-683-3511 Pri
begin Steve Lord quotation: Of course, my bad. An Emacs binary contains a bunch of C code making up the Lisp interpeter and primitive functions (subrs) and a .data section that contains pre-loaded Li
begin Sean Neakums quotation: Yep, I just got me a dumped emacs binary full of NULs with the original GNU source. -- ///////////////// | | The spark of a pin <sneakums@xxxxxxxx> | (require 'gnu) | dr
OK, bingo, I can replicate this now, I too have a bad binary, it looks like the memory is getting reclaimed without getting flushed out to disk - which is not good at all. This actually gives me some
OK, bingo, I can replicate this now, I too have a bad binary, it looks like the memory is getting reclaimed without getting flushed out to disk - which is not good at all. This actually gives me some
What is the affected version with this? 2.4.17 or all? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-698-7250 email: austin@xxxxxxxxxxxxxxx "It is the part of a good shepherd
begin Austin Gonyou quotation: I had the Emacs build failures on my 2.4.16 CVS pull, too. I haven't tried to reproduce on 2.4.16 with io-test.c and the manual Emacs dump. I haven't had the Emacs buil
Well I hit it in 2.5.2-pre7, but I suspect it goes back into 2.4.16 at least. I may have made a mistake in the changes which went in to fix various things during 2.4.16. Steve -- Steve Lord voice: +1
Sean said that 2.4.14 did not seem to be affected; it may be that a bug got pushed somewhere since then and popped out somewhere else. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projec
It looks like the problem was introduced sometime after the original split patches for 2.4.16 were put out on Dec 3rd. So it is either related to something in the fixes for dbench on low memory syste
I started with the initial 2.4.16 patches and kept applying fixes to them - so far I have not managed to reproduce the problem, so I am going to try a kernel from just before the 2.4.17 merge went in
begin Steve Lord quotation: Sure thing, I'll get that built and tested. The 2.4.16 that's failing for me was built on the 18th December. The cvs update probably didn't happen very long before that. I
begin Sean Neakums quotation: I built a Linus 2.4.16, patched for XFS with the patch from the above location, and I'm certain that the bug was not present in XFS when that patch was generated. I succ
begin Sean Neakums quotation: begin Steve Lord quotation: Sean, if you could apply the xfs patches for 2.4.16 (on oss.sgi.com in the projects/xfs/download/patches/2.4.16 directory) and see if you co
begin Stephen Lord quotation: I just found a kernel from December 8 (I had removed it from lilo.conf, but forgotten to delete the kernel itself and the modules) and I cannot recreate on that. -- ////
Sean, can you see if the attached patch against the current cvs tree fixes the problem for you? So far I have not been able to reproduce with this change. Steve -- Steve Lord voice: +1-651-683-3511 P
And here is a patch I prefer you test - since I think this is more like a real fix instead of a go back and mask the original problem again Steve -- Steve Lord voice: +1-651-683-3511 Principal Engine