Quoth Bob Grimes:
> I had tried this because of comments such as yours, Gavin (no, I am
> most certainly NOT blaming you! :) ) in a last attempt to get C++ apps
> to work, but that killed everything. (Well, okay, not everything, but
> damn, I couldn't even change or list directories!).
Well, it'l
On 9/25/07, Gavin Lambert <[EMAIL PROTECTED]> wrote:
> Quoth Jamie Lokier:
> > It might be useful to see these files, and the exact version of
> > toolchain, and exact command line, and exact compiler messages (with
> > -v option, to show exactly which libraries are used), as there aren't
> > a lot
On 9/25/07, Jamie Lokier <[EMAIL PROTECTED]> wrote:
> It might be useful to see these files, and the exact version of
> toolchain, and exact command line, and exact compiler messages (with
> -v option, to show exactly which libraries are used), as there aren't
> a lot of people reporting this probl
Jamie Lokier wrote:
Gavin Lambert wrote:
Quoth Jamie Lokier:
But this part of the kernel will relocate incorrectly in border
cases with XIP:
if (r < text_len) /* In text segment */
addr = r + start_code;
else
Quoth Jamie Lokier:
> It might be useful to see these files, and the exact version of
> toolchain, and exact command line, and exact compiler messages (with
> -v option, to show exactly which libraries are used), as there aren't
> a lot of people reporting this problem.
I used to have it quite a l
Bob Grimes wrote:
> On 9/25/07, David Wu <[EMAIL PROTECTED]> wrote:
>
> >
> > From our experience, when you get "BINFMT_FLAT: reloc outside program"
> > nomally the stack is overflow and reached the memory of another process.
> > The newer compiler seems more likely needing larger stack.
> I trie
Bob Grimes wrote:
> > e.g. something like this might cause the problem:
> >
> > int x[10];
> > int *y = &x[-1000];
> I don't have any constructs such as this.
He doesn't mean that's in your source. He means GCC may generate code
equivalent to this, as part of some optimisation.
>
Hello Bob,
On Dienstag, 25. September 2007, Bob Grimes wrote:
> On 9/25/07, David Wu <[EMAIL PROTECTED]> wrote:
> > From our experience, when you get "BINFMT_FLAT: reloc outside
> > program" nomally the stack is overflow and reached the memory of
> > another process. The newer compiler seems more
On 9/25/07, David Wu <[EMAIL PROTECTED]> wrote:
>
> From our experience, when you get "BINFMT_FLAT: reloc outside program"
> nomally the stack is overflow and reached the memory of another process.
> The newer compiler seems more likely needing larger stack.
I tried that on my app, but that didn'
On 9/24/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> > What does "BINFMT_FLAT: reloc outside program" mean, and how do I fix
> > it?
>
> It means pretty much what it says. A relocation is pointing out program text
> and data areas and the kernel is erroring out over it.
Yeah, but I don't kno
David Wu wrote:
> From our experience, when you get "BINFMT_FLAT: reloc outside program"
> nomally the stack is overflow and reached the memory of another process.
> The newer compiler seems more likely needing larger stack.
That reminds me. Are there any working GCC options to turn on
run-ti
Gavin Lambert wrote:
> Quoth Jamie Lokier:
> > But this part of the kernel will relocate incorrectly in border
> > cases with XIP:
> >
> > if (r < text_len) /* In text segment */
> > addr = r + start_code;
> > else
Hi Bob,
On Mon, 24 Sep 2007 22:50:48 -0400, Bob Grimes <[EMAIL PROTECTED]>
wrote:
What does "BINFMT_FLAT: reloc outside program" mean, and how do I fix
it? I was trying to get C++ working, but I've given up on that. Now,
I'm just trying to get back to a working kernel, and I get the same
er
Quoth Jamie Lokier:
> But this part of the kernel will relocate incorrectly in border
> cases with XIP:
>
> if (r < text_len) /* In text segment */
> addr = r + start_code;
> else/* In data segment */
>
> So basically you're saying C++ works fine, provided that simple test
> is removed from the kernel, is that right?
Nope. The message will disappear if the test is removed :-) And if you
*must* get something going that produces this message, this is the first step
along a long and painful pat
[EMAIL PROTECTED] wrote:
> > What does "BINFMT_FLAT: reloc outside program" mean, and how do I fix
> > it?
>
> It means pretty much what it says. A relocation is pointing out
> program text and data areas and the kernel is erroring out over it.
>
> The fix is to remove this test from the binfmt_f
> What does "BINFMT_FLAT: reloc outside program" mean, and how do I fix
> it?
It means pretty much what it says. A relocation is pointing out program text
and data areas and the kernel is erroring out over it.
The fix is to remove this test from the binfmt_flat loader, it is possible to
have r
17 matches
Mail list logo
