Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linker error with GDBStub #3903

Closed
chessweb01 opened this issue Dec 2, 2017 · 3 comments
Closed

Linker error with GDBStub #3903

chessweb01 opened this issue Dec 2, 2017 · 3 comments
Labels
waiting for feedback Waiting on additional info. If it's not received, the issue may be closed.

Comments

@chessweb01
Copy link

I added #include <GDBStub.h> to my sketch for NodeMCU v1.0 and got the following linker error:

.pioenvs\nodemcuv2\lib\GDBStub\internal\gdbstub.o: In function `gdbReadCommand$part$3':
gdbstub.c:(.iram.text+0x6f9): dangerous relocation: call0: misaligned call target: gdbstub_set_hw_breakpoint
gdbstub.c:(.iram.text+0x796): dangerous relocation: call0: misaligned call target: gdbstub_del_hw_watchpoint

@igrr
Copy link
Member

igrr commented Dec 27, 2017

@chessweb01 I have tested a few of the examples (Blink, FSBrowser, SPISlave_Master) and wasn't able to reproduce this issue. Please attach a sketch which demonstrates the issue.

@igrr igrr added the waiting for feedback Waiting on additional info. If it's not received, the issue may be closed. label Dec 27, 2017
@freeck
Copy link

freeck commented Jan 25, 2018

I remember that using buildflag 'long calls' introduced this linker error. That is caused by the fact that file gdbstub_init.S is word or byte-alligned. So I inserted 'align 4' before the functions. Hope this works for you.

@earlephilhower
Copy link
Collaborator

Closing with any kind of tracking in #5559

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for feedback Waiting on additional info. If it's not received, the issue may be closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants