Bug 264344 - editors/ne: Crashes on startup: uid 0: exited on signal 11 (core dumped)
Summary: editors/ne: Crashes on startup: uid 0: exited on signal 11 (core dumped)
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Wen Heping
URL:
Keywords: crash, needs-qa
Depends on:
Blocks:
 
Reported: 2022-05-30 07:47 UTC by gerrit.kuehn
Modified: 2022-06-03 08:32 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (wen)


Attachments
pkg info ne (806 bytes, text/plain)
2022-06-03 07:52 UTC, gerrit.kuehn
no flags Details
pkg version -v (5.03 KB, text/plain)
2022-06-03 07:54 UTC, gerrit.kuehn
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description gerrit.kuehn 2022-05-30 07:47:28 UTC
ne dumps core right after installation when being started on 12.3:

kernel: pid 87894 (ne), jid 0, uid 0: exited on signal 11 (core dumped
Comment 1 Wen Heping freebsd_committer freebsd_triage 2022-05-30 08:11:56 UTC
(In reply to gerrit.kuehn from comment #0)
I can not reproduce this error on 14-current, and I have no 12.3 installation :(
Comment 2 gerrit.kuehn 2022-05-30 08:44:23 UTC
Didn't see this on 13.0 and 13.1, either.
Is there anything I can help for debugging on 12.3?
Comment 3 wen 2022-05-30 12:21:35 UTC
(In reply to gerrit.kuehn from comment #2)
Maybe report it to upstream ?
Thank you !
Comment 4 gerrit.kuehn 2022-05-30 17:06:11 UTC
Sorry? As it is working fine on 13.0 and 13.1, but crashes on 12.3, this rather looks like a FreeBSD/ports issue to me. The ne project's homepage doesn't even list FreeBSD under "ports".
Also, I can remember having no issues with ne on earlier FreeBSD versions (12.1 was probably fine, but I don't have any of these left around for testing).
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2022-05-30 23:34:17 UTC
@Reporter

Could you add additional information, including:

- Whether using the port or package?
- `pkg info ne` output (as an attachment)
- `pkg version -v` output (as an attachment)
- if using the port: contents of /etc/make.conf if not empty (as an attachment)

Also and if possible, a debug build (build port WITH_DEBUG=yes), and a coredump backtrace (using devel/gdb) would be useful for isolation.

(In reply to Wen Heping from comment #1)

A test in a poudriere testport 12.3 jail might be reproducible
Comment 6 gerrit.kuehn 2022-06-03 07:52:57 UTC
Created attachment 234410 [details]
pkg info ne
Comment 7 gerrit.kuehn 2022-06-03 07:54:05 UTC
Created attachment 234411 [details]
pkg version -v
Comment 8 gerrit.kuehn 2022-06-03 08:00:00 UTC
Up to now, this was all done using the packaged version. I built a debug version now (with empty make.conf) that reports

root:~ # ne
ne.c:183:8: runtime error: applying non-zero offset 8 to null pointer
SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ne.c:183:8 in 
AddressSanitizer:DEADLYSIGNAL
=================================================================
==44213==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x000000464273 bp 0x7fffffffeab0 sp 0x7fffffffe8c0 T0)
==44213==The signal is caused by a READ memory access.
==44213==Hint: address points to the zero page.
    #0 0x464273 in main (/usr/local/bin/ne+0x464273)
    #1 0x2a823f in _start (/usr/local/bin/ne+0x2a823f)
    #2 0x800530fff  (<unknown module>)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/usr/local/bin/ne+0x464273) in main
==44213==ABORTING


However, I don't get a core dump that I could use gdb on?! I get coredumps for the package version, but these are pretty useless as they lack the debug symbols. Am I doing something wrong?
Comment 9 gerrit.kuehn 2022-06-03 08:32:13 UTC
(In reply to Kubilay Kocak from comment #5)

I added all info I could gather. Is there any reason why I don't get a corefile anymore after enabling debug symbols?