> On Nov 21, 2021, at 6:35 AM, John Marino (NetBSD) wrote:
>
> Sorry, I meant to answer and got overwhelmed.
> Actually, I had a typo in the previous response. I meant to say "GCC"
> unwinder, not gdb unwinder.
> I don't see how this helps support the GCC unwinder. The context information
>
I'm not very familiar with CFA information. I've been worried that
strip(1) removes those symbols. Is that worry meritless?
On Sun, Nov 21, 2021 at 9:32 AM Jason Thorpe wrote:
>
> > On Nov 21, 2021, at 6:35 AM, John Marino (NetBSD)
> wrote:
> >
> > Sorry, I meant to answer and got
Hello,
Here is what I try to accomplish. I could not find the bios for the
0x1002/0x6604 device. So I thought that I could just disable this
device, and use the Kaveri device (0x1002/0x1309), since I have that
bios.
I have put the two files listed above (by RVP) to the
Sorry, I meant to answer and got overwhelmed.
Actually, I had a typo in the previous response. I meant to say "GCC"
unwinder, not gdb unwinder.
I don't see how this helps support the GCC unwinder. The context
information to support the unwind is already provided, we just need the
boolean (is this
Riza Dindir wrote:
>I have put the two files listed above (by RVP) to the
>"src/sys/dev/microcode/radeon/" directory. I also changed the
>configuration to only include the radeon device that is the
>0x1002/0x1309 Kaveri device. Did add the KAVERI_mec2.bin to the
>MODULE_FIRMWARE definitions in
> On Nov 21, 2021, at 8:28 AM, Jason Thorpe wrote:
>
> If strip removes it, then you’re doomed anyway and trampoline assist via a
> function won’t help you, because you won’t be able to get to the trampoline
> or past it anyway.
Here’s a before/after of a “strip -s” of a binary on the
If strip removes it, then you’re doomed anyway and trampoline assist via a
function won’t help you, because you won’t be able to get to the trampoline or
past it anyway.
-- thorpej
Sent from my iPhone.
> On Nov 21, 2021, at 7:54 AM, John Marino (NetBSD) wrote:
>
>
> I'm not very familiar
