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

llegal character '}' I think its there is no input sanitization done #38

Closed
leftehjam opened this issue Nov 7, 2020 · 2 comments
Closed
Labels
bug missing-info More information needed

Comments

@leftehjam
Copy link

leftehjam commented Nov 7, 2020

No description provided.

@leftehjam leftehjam changed the title No String sanitization llegal character '}' Nov 7, 2020
@leftehjam
Copy link
Author

  • [1.4.4 ] What version of freerouting are you using?
  • [Windows ] On what platform did you run it? Windows, Linux, MacOS? 32-bit or 64-bit?
  • [ DSN] What type of file are you working with? Can you attach the actual (DSN) file?
  • [N ] Did you use any command line arguments?
  • [ soon] Can you post a screenshot of the problem?
  • Can you include the latest, related log entries from the .log file?
    [AWT-EventQueue-0] ERROR eu.mihosoft.freerouting.FreeRouting - Illegal character '}' was found at position 9780
  • [ not sure atm ] Please list the detailed steps to reproduce the problem
  • [ launch] What would you expect freerouting to do in this situation?
  • [not critical but would make program launch ] Is fixing this issue critical for your work?

image

@leftehjam leftehjam changed the title llegal character '}' llegal character '}' I think its there is no input sanitization done Nov 7, 2020
@leftehjam
Copy link
Author

leftehjam commented Nov 7, 2020

Checking dsn file reveals 2 things of note. kicad does use " " for special characters if it is " there is no special character marker around " its just ".
IF you rename your nodes (in KiCad) it will change the error to the class section at the bottom of the dsn file (class kicad_default "" " 0 1 1.8v 2 ....... } ) The only way to fix this bug is to delete the current PcbNew file re change the offending nodes and then reload PcbNew.

@andrasfuchs andrasfuchs added the bug label Nov 7, 2021
@andrasfuchs andrasfuchs added the missing-info More information needed label May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug missing-info More information needed
Projects
None yet
Development

No branches or pull requests

2 participants