QeMU breaking after GCC upgrade
I've been developing for PowerPC systems for a while now and until recently have been relying on GCC 6.3, without problems.
Currently, due to different reasons, I had to switch from GCC 6.3 to GCC 8.2
Now, my system is working just fine for the development board (MPC5777) but when I use QeMU it no longer works. I have tried with QeMU 2.8, 2.12 and 3.1, with the same result. so the problem is not with QeMu (I think).
QEMU 2.8.50 monitor - type 'help' for more information
(qemu) rom: requested regions overlap (rom Executables/Partition2.elf. free=0x000000000049659c, addr=0x0000000000128000)
C:Program Filesqemuqemu-system-ppc.exe: rom check and register reset failed
make[1]: *** [makefileQeMU:89: run] Error 1
I have looked around for a solution, but haven't found anything significant. I have read some things talking about the linker script being the issue, but it does not seem to be right, as the addresses should be the same and the only thing I have changed is the compiler version.
qemu powerpc ppc
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
add a comment |
I've been developing for PowerPC systems for a while now and until recently have been relying on GCC 6.3, without problems.
Currently, due to different reasons, I had to switch from GCC 6.3 to GCC 8.2
Now, my system is working just fine for the development board (MPC5777) but when I use QeMU it no longer works. I have tried with QeMU 2.8, 2.12 and 3.1, with the same result. so the problem is not with QeMu (I think).
QEMU 2.8.50 monitor - type 'help' for more information
(qemu) rom: requested regions overlap (rom Executables/Partition2.elf. free=0x000000000049659c, addr=0x0000000000128000)
C:Program Filesqemuqemu-system-ppc.exe: rom check and register reset failed
make[1]: *** [makefileQeMU:89: run] Error 1
I have looked around for a solution, but haven't found anything significant. I have read some things talking about the linker script being the issue, but it does not seem to be right, as the addresses should be the same and the only thing I have changed is the compiler version.
qemu powerpc ppc
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
add a comment |
I've been developing for PowerPC systems for a while now and until recently have been relying on GCC 6.3, without problems.
Currently, due to different reasons, I had to switch from GCC 6.3 to GCC 8.2
Now, my system is working just fine for the development board (MPC5777) but when I use QeMU it no longer works. I have tried with QeMU 2.8, 2.12 and 3.1, with the same result. so the problem is not with QeMu (I think).
QEMU 2.8.50 monitor - type 'help' for more information
(qemu) rom: requested regions overlap (rom Executables/Partition2.elf. free=0x000000000049659c, addr=0x0000000000128000)
C:Program Filesqemuqemu-system-ppc.exe: rom check and register reset failed
make[1]: *** [makefileQeMU:89: run] Error 1
I have looked around for a solution, but haven't found anything significant. I have read some things talking about the linker script being the issue, but it does not seem to be right, as the addresses should be the same and the only thing I have changed is the compiler version.
qemu powerpc ppc
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
I've been developing for PowerPC systems for a while now and until recently have been relying on GCC 6.3, without problems.
Currently, due to different reasons, I had to switch from GCC 6.3 to GCC 8.2
Now, my system is working just fine for the development board (MPC5777) but when I use QeMU it no longer works. I have tried with QeMU 2.8, 2.12 and 3.1, with the same result. so the problem is not with QeMu (I think).
QEMU 2.8.50 monitor - type 'help' for more information
(qemu) rom: requested regions overlap (rom Executables/Partition2.elf. free=0x000000000049659c, addr=0x0000000000128000)
C:Program Filesqemuqemu-system-ppc.exe: rom check and register reset failed
make[1]: *** [makefileQeMU:89: run] Error 1
I have looked around for a solution, but haven't found anything significant. I have read some things talking about the linker script being the issue, but it does not seem to be right, as the addresses should be the same and the only thing I have changed is the compiler version.
qemu powerpc ppc
qemu powerpc ppc
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
edited Jan 4 at 21:07
Felipe GM
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
asked Jan 4 at 16:26
Felipe GMFelipe GM
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I was able to find a (somehow) solution to this. When compiling, I am using -g3 flag for debugging purposes. using it with GCC 6.3 didn't seem to increase my file (.elf) size that much. Now, with 8.2 the size difference was HUGE, leading to the memory overlap. As I was not taking into account that this could happen, when loading the elf files into QeMU, I was not reserving enough memory space.
I will investigate deeper the reason for so much difference on the debugging information created and update this post, but if someone with the same problem ends up here, please do consider this kind of situation.
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390600%2fqemu-breaking-after-gcc-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to find a (somehow) solution to this. When compiling, I am using -g3 flag for debugging purposes. using it with GCC 6.3 didn't seem to increase my file (.elf) size that much. Now, with 8.2 the size difference was HUGE, leading to the memory overlap. As I was not taking into account that this could happen, when loading the elf files into QeMU, I was not reserving enough memory space.
I will investigate deeper the reason for so much difference on the debugging information created and update this post, but if someone with the same problem ends up here, please do consider this kind of situation.
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
add a comment |
I was able to find a (somehow) solution to this. When compiling, I am using -g3 flag for debugging purposes. using it with GCC 6.3 didn't seem to increase my file (.elf) size that much. Now, with 8.2 the size difference was HUGE, leading to the memory overlap. As I was not taking into account that this could happen, when loading the elf files into QeMU, I was not reserving enough memory space.
I will investigate deeper the reason for so much difference on the debugging information created and update this post, but if someone with the same problem ends up here, please do consider this kind of situation.
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
add a comment |
I was able to find a (somehow) solution to this. When compiling, I am using -g3 flag for debugging purposes. using it with GCC 6.3 didn't seem to increase my file (.elf) size that much. Now, with 8.2 the size difference was HUGE, leading to the memory overlap. As I was not taking into account that this could happen, when loading the elf files into QeMU, I was not reserving enough memory space.
I will investigate deeper the reason for so much difference on the debugging information created and update this post, but if someone with the same problem ends up here, please do consider this kind of situation.
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
I was able to find a (somehow) solution to this. When compiling, I am using -g3 flag for debugging purposes. using it with GCC 6.3 didn't seem to increase my file (.elf) size that much. Now, with 8.2 the size difference was HUGE, leading to the memory overlap. As I was not taking into account that this could happen, when loading the elf files into QeMU, I was not reserving enough memory space.
I will investigate deeper the reason for so much difference on the debugging information created and update this post, but if someone with the same problem ends up here, please do consider this kind of situation.
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
answered Jan 7 at 21:22
Felipe GMFelipe GM
63
63
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390600%2fqemu-breaking-after-gcc-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
