Summary: | dev-util/aruba-2.2.0 fails tests on hppa: /usr/lib/ruby/gems/3.1.0/gems/cucumber -cucumber-expressions-17.0.1/lib/cucumber/cucumber_expressions/group_builder.rb:20: [BUG] Segmentation fault at 0xf888701c | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | matoro <matoro_gentoo> |
Component: | Current packages | Assignee: | Hans de Graaff <graaff> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | hppa, matoro_gentoo, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | HPPA | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=935293 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 916520 | ||
Attachments: | build.log and emerge --info |
Description
matoro
2024-02-17 15:56:32 UTC
Created attachment 885226 [details]
build.log and emerge --info
I'm not sure what it's really crashing in. Do you get a better backtrace under gdb? Also, do dev-ruby/ffi tests pass? (I notice it in the list of loaded modules) Unfortunately I can't seem to get anything out of it with gdb. When I run it directly under gdb it seems to fail to attach, the process keeps running in the background and I get a blank gdb prompt. If I just let it die and pick up the postmortem core it only shows the error handler: $ gdb -q -c ./core -se /usr/bin/ruby31 Reading symbols from /usr/bin/ruby31... [New LWP 3332] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Core was generated by `/usr/bin/ruby31 -S cucumber --color --format progress --tags not @wip'. Program terminated with signal SIGABRT, Aborted. #0 0x000004e4 in ?? () (gdb) bt #0 0x000004e4 in ?? () #1 0xf810a884 in ?? () from /lib/libc.so.6 #2 0xf80b8058 in raise () from /lib/libc.so.6 #3 0xf80a0878 in abort () from /lib/libc.so.6 #4 0xf841a16c in die () at error.c:784 Backtrace stopped: Cannot access memory at address 0xcf0 So, unlikely to be able to easily fix. Any options for unkeywording? (In reply to matoro from comment #3) > Unfortunately I can't seem to get anything out of it with gdb. When I run > it directly under gdb it seems to fail to attach, the process keeps running > in the background and I get a blank gdb prompt. > Try playing with https://sourceware.org/gdb/current/onlinedocs/gdb.html/Forks.html. I would try set follow-fork-mode child. (In reply to Sam James from comment #4) > (In reply to matoro from comment #3) > > Unfortunately I can't seem to get anything out of it with gdb. When I run > > it directly under gdb it seems to fail to attach, the process keeps running > > in the background and I get a blank gdb prompt. > > > > Try playing with > https://sourceware.org/gdb/current/onlinedocs/gdb.html/Forks.html. > > I would try set follow-fork-mode child. Sorry, should have specified, this is even with follow-fork-mode child. bleh, a shame, but I can't promise to look at it atm. It looks like dekeywording might be possible.. We dropped ruby on hppa. What about bug 916520 then? |