8000 x86 DEBUG=1 build traps/segfaults on Ctrl+C · Issue #1035 · micropython/micropython · GitHub
[go: up one dir, main page]
Skip to content

x86 DEBUG=1 build traps/segfaults on Ctrl+C #1035

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.

Sign up for GitHub

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

Jump to bottom
Closed
pfalcon opened this issue Jan 2, 2015 · 1 comment
Closed

x86 DEBUG=1 build traps/segfaults on Ctrl+C #1035

pfalcon opened this issue Jan 2, 2015 · 1 comment
Labels
ports Relates to multiple ports, or a new/proposed port

Comments

@pfalcon
Copy link
Contributor
pfalcon commented Jan 2, 2015

FWIW, "make DEBUG=1 MICROPY_FORCE_32BIT=1" build run on x64, when run following test script:

while True:
    pass

and being Ctrl+C'ed, fails with:

Trace/breakpoint trap (core dumped)

Previous builds also segfaulted there (i.e. looks like it jumps somewhere random).

This is all with:

gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
@pfalcon pfalcon added the ports Relates to multiple ports, or a new/proposed port label Jan 2, 2015
@pfalcon
Copy link
Contributor Author
pfalcon commented Dec 18, 2015

Fixed by 3db2b23.

@pfalcon pfalcon closed this as completed Dec 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ports Relates to multiple ports, or a new/proposed port
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pfalcon
0