| Summary: | www-client/firefox crashes on musl-amd64 when attached to gdb - src/thread/x86_64/syscall_cp.s: No such file or directory. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | tt_1 <herrtimson> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
backtrace
emerge.info |
||
Created attachment 430458 [details]
emerge.info
The backtrace does not indicate any crash at all. Does "crash" mean "segmentation fault"? What versions of firefox and gdb are used? I cannot reproduce the issue on an arm system with musl. I'm not really sure if this is a bug or not, but it is complaining about something important (?) missing and I wanted it to post here. If it is invalid or more information is needed, just let me know. The firefox gui freezes while attaching it to gdb. gdb is trying to show the relevant line from musl's source code but can't because it can't find the source code. This is expected since musl's source code is not installed. The same applies to the other libraries. It is expected that a process is stopped when attaching gdb. Thus, the GUI will freeze until the process is continued. Ah, okay, so it is a normal and excepted behavior of gdb. sorry for the noise! |
Created attachment 430454 [details] backtrace I'm not sure if this is a bug in gdb, musl or firefox. But I have added a backtrace for convenience! It happens when I start firefox and later on use the command gdb attach #process-id