Thank you for the discussion, Luc and Tao.
This helps a lot, we can decide what to do next.
Thanks
Lianbo
On Thu, Nov 13, 2025 at 5:03 AM ltao <ltao(a)redhat.com> wrote:
Hi Luc,
Thanks for your comments!
On Thu, Nov 13, 2025 at 4:33 AM Luc Park-Chouinard <lucchouina(a)gmail.com>
wrote:
>
> Hi Tao, Lianbo,
>
> eppic.c is the glue between a release cycle for crash and ongoing
changes to eppic v5.0. That file is yours and you can commit to it freely.
> I can grant commit access to you guys to remove the delays due to TZ or
availability.
Thanks for that, please add me in, my github account is liutgnu.
>
> One could even ask the question - if eppic.c should just be on the crash
repo side. But I still believe there is benefit to have it be part of eppic
to reduce backward/forward comp issues.
>
> I like the proposed crash-dev changes. Never realized dlopen(NULL) was
for /proc/self... Cool.
> The more flexibility in what we can do, the better.
OK, good to know your thoughts! Then I will delete the empty
eppic.patch file in the crash repo side. And I will do the new feature
testing/developing in my eppic forked repo first. Once it is ready to
go, I will push it to your upstream eppic repo.
Thanks again for your help on this!
Thanks,
Tao Liu