-----Original Message----- > After applied the v3 series based on the latest crash, I got the following > error: > > # crash vmlinux vmcore ... > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from 3.10.0-957.el7.x86_64/vmlinux... > thread.c:95: internal-error: thread_info* inferior_thread(): Assertion > `current_thread_ != nullptr' > failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) n > > This is a bug, please report it. > > thread.c:95: internal-error: thread_info* inferior_thread(): Assertion > `current_thread_ != nullptr' > failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Create a core file of GDB? (y or n) y > Command aborted. > #
This error is same as the issue I reported for the v2: https://www.redhat.com/archives/crash-utility/2020-December/msg00031.html It does not occur without the 2/2 patch at my end, can you try? Alexey, is there any update on this? > > We would make sure that the crash has good backward compatibility. > > I didn't test the functions yet, there may be another issues. In view of > this, I would suggest temporarily > putting the patch series in our reviewing queue, because this is a big change > and need to handle it carefully. > > Currently, I'm planning to improve the test cases. Once the test is ready, > which can help us find out more > potential issues. And we can improve it based on this series. What do you > think? Kazu, Bhupesh and Alexey. I's great to improve the test cases, thanks. but do you mean we wait until the new test is ready? Thanks, Kazu -- Crash-utility mailing list Crash-utility@redhat.com https://www.redhat.com/mailman/listinfo/crash-utility
