Debugging Compiler Issues

[Gavin Kavanaugh <zeddicus76 at gmail dot com>]

First of all I love the crosstool-NG. I used the original one years ago 
and I didn't have any idea it was being updated and maintained. Nice work.

I ran across the update because I am trying to dig into an issue and it 
seems like I should be able to do it with crosstool-NG. If anyone can 
help me out I would greatly appreciate it.

The problem is that I have an application that is running on many 
different distributions. But when I run it on the latest openSUSE 11.3 
release I get an assert at start up. After some local debugging I find 
that this assert is showing up before I even get to the main function of 
my app. I have done enough debugging to be fairly certain that this 
issue is in glibc, or gcc.  So what I wanted to do was set up a build so 
I could build gcc, glibc, and whatever else I needed to a specific 
version and see if the issue reproduces. Then I can tweak the library 
versions to help me determine the root cause.

I think what I want is to use crosstool-NG to generate a native 
compiler, but that is not supported(?). Instead I have generated a 
cross-compiler which is for my host machine. I am able to compile my 
application using this new cross-compiler, but running it just leads to 
problems because of library dependency. I thought about setting up a 
chroot environment for my new toolchain but I have not done this before 
and I'm not sure it's the best solution either.

Hopefully that is enough detail to get my point across. Does anyone know 
how to set this up?
Thank you in advance,
Gavin



--
For unsubscribe information see http://sourceware.org/lists.html#faq