Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: closed Priority: high | Milestone: 6.10.1 Component: GHCi |Version: 6.9 Severity: normal | Resolution: duplicate Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Changes (by simonmar): * status: reopened = closed * resolution: = duplicate Comment: already open as #2063. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:19 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: reopened Priority: high | Milestone: 6.10.1 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Changes (by igloo): * status: closed = reopened * resolution: fixed = * milestone: 6.8.3 = 6.10.1 Comment: This still needs to be fixed in the 6.10 branch, right? And see also #2351. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:18 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: closed Priority: high | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: fixed Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Changes (by simonmar): * status: new = closed * resolution: = fixed Comment: I pushed (a slight variant of) 2013.patch. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:17 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: new Priority: high | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Changes (by simonmar): * priority: normal = high -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:16 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): The patch is a proof of concept, it needs someone to clean it up (i.e. `#ifdef freebsd` the changes, basically). Also something different needs to be done for HEAD, so after fixing this in 6.8.3 we need to move the ticket onto the 6.10 milestone. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:15 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: simonmar Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Changes (by igloo): * owner: = simonmar Comment: Simon, what's the status of this? Should we apply the patch for 6.8.3? -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:14 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): See also #2195 -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:13 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): Thanks for the patch! I'll take a look. Your patch will apply to 6.8.3, but in HEAD the previously mentioned patch add PIC relocations for x86_64 has been applied, and the `x86_64_high_symbol()` hack has been replaced by the `symbol_extras` stuff. If you were able to port your changes to the HEAD too, that would be great. Currently the HEAD will not compile at all on x86_64 non-Linux. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:11 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by wb.kloke): I can confirm that the patch is good for use for most of the testsuite with my system. I updated my FreeBSD-7.0-amd64 binary dist with the patch applied, and the testsuite output. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:12 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): Replying to [comment:7 mboes]: Good news: I have a working ghci loading base and giving me a prompt! This is done by adding MAP_FIXED to the EXTRA_MAP_FLAGS and giving a hint address, both in loadObj() and in x64_64_high_symbol(). Of course, ghci segfaults the minute you try to link in more packages, because new objects will overwrite the old ones in memory at the fixed address. The upshot is that forcing 32-bit clean mmap()'s is the only issue needing solving for ghci on FreeBSD/amd64. All the bugs I used to see with 6.6.1 (eg. race conditions with writing characters to the screen) are now gone. The trick to solve this issue is to calculate a valid place in memory to mmap() objects in, large enough for the whole object, that does not conflict with anything else living in memory. Simon, any suggestions as to the best way to do that? At the moment I'm loading the object at the 1Gb boundary, and looking around on the web that's the way that Xorg project are working around their need for a MAP_32BIT flag on NetBSD. It's an ugly hack, but I don't see any other way of dealing with a lack of MAP_32BIT. We could increment the load address by oc-fileSize + space for jump islands at each object load, so that all objects are somewhere above the 1Gb mark. Then create jump islands for each loaded object directly after it in memory. However, if we're loading so much in memory at fixed locations we'd have to be very sure that nothing else is allocated above the 1Gb mark before the linking. How feasible is this? This is encouraging. It looks like the solution is going to be dependent on the layout of memory on FreeBSD and hence might be fragile to future changes in that area, but it's better than nothing. You want to look at the memory map of the running process to figure out where the best place to allocate memory is. On Linux the memory map is available in `/proc/pid/maps` for process `pid`. Note that `MBlock.c` also allocates memory using `mmap`, you probably want to check that it isn't accidentally grabbing some of the sub-2Gb memory which would cause problems for the linker. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:9 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by mboes): Hi, I have a short patch for this, attached. I have a rather slow connection at the moment and downloading the stable darcs branch is going to be taking a few days at this rate so the patch is a unified diff relative to 6.8.2 release, rather than a darcs patch. Sorry about that! On my system ghci never seems to be loaded with anything allocated in the 1-2GB segment. This patch makes ghci load all objects starting from 1GB growing upwards, one after the other. Loading will fail if there is anything in the way, but I haven't seen this to be a problem on my machine and besides linking happens very early in the lifetime of a ghci process. The jump islands for symbols in shared libs loaded in high mem are allocated starting from the 2GB mark, growing downwards. Let me know if you'd like to see any revisions to this patch. Regards, Mathieu -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:10 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): Setting milestone to 6.8.3 as we would like GHCi to work properly on FreeBSD/x86-64. I don't have any good suggestions yet. Object code that is not compiled with `-fPIC` must be all linked together in the same 2Gb segment of the address space, because 32-bit relative addressing is used throughout. We use the small memory model by default, like gcc - I haven't investigated using larger memory models, but in any case `-fPIC` would be better than moving to another memory model as it is already implemented. Unfortunately `-fPIC` doesn't really solve the problem - even objects compiled with `-fPIC` assume that other objects in the same package are within the same 2Gb segment. So we really do need a way to map memory in the low 2Gb. As far as I can tell, the only way to do this when MAP_32BIT is not supported is with the hint address - perhaps look at the memory map of the running process, and figure out a suitable place to request memory? It might be necessary to coordinate with `MBlock.c` to avoid requesting memory in the low 2Gb when we don't need it. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:5 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by wb.kloke): Is it feasible to link packages like base statically to ghci to get ghci working for simple programs not loading modules? Or else, as base is already wired-in, is the loading of base necessary at all? -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.9 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by mboes): Good news: I have a working ghci loading base and giving me a prompt! This is done by adding MAP_FIXED to the EXTRA_MAP_FLAGS and giving a hint address, both in loadObj() and in x64_64_high_symbol(). Of course, ghci segfaults the minute you try to link in more packages, because new objects will overwrite the old ones in memory at the fixed address. The upshot is that forcing 32-bit clean mmap()'s is the only issue needing solving for ghci on FreeBSD/amd64. All the bugs I used to see with 6.6.1 (eg. race conditions with writing characters to the screen) are now gone. The trick to solve this issue is to calculate a valid place in memory to mmap() objects in, large enough for the whole object, that does not conflict with anything else living in memory. Simon, any suggestions as to the best way to do that? At the moment I'm loading the object at the 1Gb boundary, and looking around on the web that's the way that Xorg project are working around their need for a MAP_32BIT flag on NetBSD. It's an ugly hack, but I don't see any other way of dealing with a lack of MAP_32BIT. We could increment the load address by oc-fileSize + space for jump islands at each object load, so that all objects are somewhere above the 1Gb mark. Then create jump islands for each loaded object directly after it in memory. However, if we're loading so much in memory at fixed locations we'd have to be very sure that nothing else is allocated above the 1Gb mark before the linking. How feasible is this? -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:7 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range. -+-- Reporter: mboes| Owner: Type: bug | Status: new Priority: normal | Milestone: 6.8.3 Component: GHCi |Version: 6.8.1 Severity: normal | Resolution: Keywords: | Difficulty: Unknown Testcase: | Architecture: x86_64 (amd64) Os: FreeBSD | -+-- Comment (by simonmar): See also Greg Wright's email in which he mentions exactly this problem: [http://www.haskell.org/pipermail/glasgow-haskell- users/2007-April/012291.html] In the HEAD, the fragment of code mentioned above is now gone, in favour of a more general mechanism. You want the patch entitled add PIC relocations for x86_64, and use a simpler hack in place of x86_64_high_symbol() from HEAD. However, this on its own won't be enough: when we allocate memory for objects with `mmap()`, we need to get memory in the low 2Gb, which is why we use `MAP_32BIT` on Linux. I'm not sure what the right way to do this on *BSD is, but you could try adding a hint address to the `mmap()` call, something in the low 2Gb, as Greg suggested in his mail above. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler___ Glasgow-haskell-bugs mailing list Glasgow-haskell-bugs@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Re: [GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range.
-+--
Reporter: mboes| Owner:
Type: bug | Status: new
Priority: normal | Milestone: 6.8.3
Component: GHCi |Version: 6.8.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: x86_64 (amd64)
Os: FreeBSD |
-+--
Comment (by mboes):
Debug output of
{{{
./stage2/ghc-inplace --interactive +RTS -Dl 21 | tee log
}}}
is at [http://code.haskell.org/~mboes/log.bz2] (log too big for attachment
on trac).
Note that FreeBSD, just like OpenBSD, does not define MAP_32BIT and
MAP_ANONYMOUS. I see in Linker.c the following #define:
{{{
#if defined(x86_64_HOST_ARCH) defined(MAP_32BIT)
#define EXTRA_MAP_FLAGS MAP_32BIT
#else
#define EXTRA_MAP_FLAGS 0
#endif
}}}
But then I see an attempt to resolve symbols allocated in high memory
using a bounce sequence:
{{{
// On x86_64, 32-bit relocations are often used, which requires that
// we can resolve a symbol to a 32-bit offset. However, shared
// libraries are placed outside the 2Gb area, which leaves us with a
// problem when we need to give a 32-bit offset to a symbol in a
// shared library.
//
// For a function symbol, we can allocate a bounce sequence inside the
// 2Gb area and resolve the symbol to this. The bounce sequence is
// simply a long jump instruction to the real location of the symbol.
//
// For data references, we're screwed.
//
...
static void*
x86_64_high_symbol( char *lbl, void *addr )
{
x86_64_bounce *bounce;
if ( x86_64_bounce_buffer == NULL ||
x86_64_bb_next_off = X86_64_BB_SIZE ) {
x86_64_bounce_buffer =
mmap(NULL, X86_64_BB_SIZE * sizeof(x86_64_bounce),
PROT_EXEC|PROT_READ|PROT_WRITE,
MAP_PRIVATE|EXTRA_MAP_FLAGS|MAP_ANONYMOUS, -1, 0);
if (x86_64_bounce_buffer == MAP_FAILED) {
barf(x86_64_high_symbol: mmap failed);
}
x86_64_bb_next_off = 0;
}
...
}}}
Since there is no MAP_32BIT on FreeBSD it would seem the above bounce
sequence can get arbitrarily allocated in high memory. Could this be the
problem? I'm way out of my depth here, so please forgive the daftness of
this question, but on my system there are no 32bit libraries at all, only
64bit ones. Hence, could we do away with 32bit relocations entirely?
Hope this helps,
Mathieu
--
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013#comment:2
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
[GHC] #2013: ghci crash on startup: R_X86_64_32S relocation out of range.
#2013: ghci crash on startup: R_X86_64_32S relocation out of range.
---+
Reporter: mboes | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: GHCi| Version: 6.8.1
Severity: normal |Keywords:
Difficulty: Unknown |Testcase:
Architecture: x86_64 (amd64) | Os: FreeBSD
---+
On freebsd-7.0 I have a working ghc-6.8.2 bootstrapped from a ghc-6.6.1
itself boostrapped from a 32-bit machine. I'd like to create a bindist for
this platform, for which there are as yet no available binary distribution
of ghc, but before that it would be nice if ghci worked. Currently I get
the following error:
{{{
[EMAIL PROTECTED]:~/ ghci
GHCi, version 6.8.2: http://www.haskell.org/ghc/ :? for help
ghc-6.8.2: internal error: R_X86_64_32S relocation out of range: (noname)
= 0x802d779c0
(GHC version 6.8.2 for x86_64_unknown_freebsd)
Please report this as a GHC bug:
http://www.haskell.org/ghc/reportabug
[1]21394 abort ghci
}}}
This bug has also been spotted before by [http://www.haskell.org/pipermail
/cvs-ghc/2007-November/039305.html Tim Newsham] on ghc-6.8.1 on Freebsd-
amd64 as well. Could this be related to #1562 or #1073 on Linux?
--
Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/2013
GHC http://www.haskell.org/ghc/
The Glasgow Haskell Compiler___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
