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

aborted core dumped after success printing #2

Open
dlwlrma00 opened this issue Jan 26, 2022 · 1 comment
Open

aborted core dumped after success printing #2

dlwlrma00 opened this issue Jan 26, 2022 · 1 comment

Comments

@dlwlrma00
Copy link

dlwlrma00 commented Jan 26, 2022

Any idea regarding this error?

Im using ubuntu 20.04 Server
[email protected]
[email protected]

Screen Shot 2022-01-27 at 1 54 56 AM

npm logs : 
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/dlwlrma/ipp_server/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle [email protected]~start: CWD: /home/dlwlrma/ipp_server
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node ./bin/www' ]
11 silly lifecycle [email protected]~start: Returned: code: 134  signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node ./bin/www`
13 verbose stack Exit status 134
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:314:20)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:314:20)
13 verbose stack     at maybeClose (internal/child_process.js:1022:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/dlwlrma/ipp_server
16 verbose Linux 5.4.0-96-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
18 verbose node v12.22.9
19 verbose npm  v6.14.15
20 error code ELIFECYCLE
21 error errno 134
22 error [email protected] start: `node ./bin/www`
22 error Exit status 134
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 134, true ]
@ThinhVu
Copy link
Owner

ThinhVu commented Jan 28, 2022

Dear @dlwlrma00

The purpose of this library is just provide some helpful functions to generate binary data for TSC Printer.

The implementation in XPrinter.js is just for demo purpose and I'm not ensure that it will work for all variety TSC devices.

Look like you already fix this error in forked branch. Can you make a PR so I can merge it to my repo so a newcomers may get benefit from it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants