-
Notifications
You must be signed in to change notification settings - Fork 68
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
output debug symbols for STM8 #162
Comments
Maybe you need apply I'll fix this later |
I've tryed that too. Doesn't work either.
So there is something to fix? No need for hurry. I'm glad if I can help improving. |
Because i found that I have fixed this in v3.9.0 You can use |
This is an unusual mistake When i use sdcc v4.2.0, it tell me this error But debugging information already exists in ELF When i use sdcc v4.0.0, it works I think the SDCC has some errors in processing debugging information in lib files. In eide builder, after compiled all c source files, eide will make a lib file (named: no_entry_bundled.lib) from all .rel file (not contain main.rel) And then, eide will use a command like Because this operation will help sdcc reduce image size, ref: https://sourceforge.net/p/sdcc/discussion/1865/thread/e395ff7a42/#a03e |
Yeah, I can confirm that the debugger plugin doesn't complain about "DWARF error" when I use SDCC v4.0.0. However, v4.0..0 seems to generate different assembly code too. After switching back I was not even able to get my super simple "blinky" program to run with release config. The debugger plugin doesn't work too. With v4.2.0 the LED is blinking when built in "release" config and manually compiled I'm able to debug the code, at least with manually started openocd (see here). So using the outdated compiler is not satisfying at all. Attached both .lst files from my blinky program:
Is it possible to make a switch for activating and deactivating this feature? At least for my simple blinky program the .elf file generated by eide is some bytes bigger than that one I compiled manually. See below: |
I can sure that compiler have no problems, because this plug-in was use v4.0.0 at the beginning
Sorry, I have no such plans in the near future I think debug feature is not very necessary for sdcc, because sdcc does not well in debug. And the |
I've the impression that the additional label(?)
I see and I accept that. Then do you have a hint for me, why the same, yet very simple, code doesn't work in v4.0.0? Thanks. |
I'm still struggeling with debugging a STM8S target. It seems to me that eide doesn't pass the proper arguments to sdcc for generating debug symbols. The STM8 debug plugin complains about DWARF error:
If I compile the program manually by entering the commands into the terminal the debug plugin works like expected.
Unfortunately I sill haven't found out how to output the exact commands and arguments that are used when compiling.
The text was updated successfully, but these errors were encountered: