[LV] Status of the toolchain build scripts?

[Jan-Benedict Glaw]

On Tue, 2007-06-19 11:26:50 +0200, Mikkel Lauritsen <mikkel-vax at tala.dk> wrote:
[...]
> Having done this, I now have a piece of GCC generated assembly code that
> makes the assember go boom - or rather, causes glibc to emit a message
> about having detected memory corruption.

I trust glibc here.

> The backtrace seems pretty innocuous; I'd be more than happy to provide it
> (or the assembly code) to anybody who has deeper insight into the inner
> workings of the assembler.
> 
> I have bisected the input file, and as long as there are no more than 1102
> lines in it the assembler works fine. Increasing the number of lines causes
> a segmentation fault, followed by the memory corruption if I increase the
> size even further.

Is it really depend it on number of lines?  Would be more plausible if
it was a simple filesize problem.

> So - my initial conclusion is that the assembler has a memory management
> problem, and I'm going to try to see if I can dig deeper into it.

Would you cut'n'paste gas's backtrace? Maybe it's possible to guess
the cause for the corruption by seeing where it crashes afterwards.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw at lug-owl.de              +49-172-7608481
  Signature of:                          Zensur im Internet? Nein danke!
  the second  :
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lug-owl.de/pipermail/vax-linux/attachments/20070619/b866acf2/attachment.pgp>
-------------- next part --------------
_______________________________________________
Linux-Vax mailing list
Linux-Vax at pergamentum.com
http://www.pergamentum.com/mailman/listinfo/linux-vax