This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: I am getting SIGSEGV in alloca, what could be the cause ?


Hi Mayank,

But the same GNU packages compile and run well without issues with an older linker.

Is it only the linker that you change in order to make things work ? If you are changing the linker and the compiler and maybe even the libraries that are linked in, then any of these things could be the source of the problem.


Or it could still be a problem in your code which is only being exposed by the newer linker. Without more information it is impossible to say.

By the way release 2.18 is now out, so please give that a go and see if it changes anything for you. If it does not then the best way to proceed is to put together a *small* testcase that reproduces the problem and then to post it to this list.

Is it because the program is running out of stack space or is there some other reason.

Almost certainly some other reason. Running out of stack space is a very rare bug, and one that you can usually check for quite easily by increasing the amount of stack space available to the process.


Cheers
  Nick


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]