Re: RISC-V support

2019-01-12 Thread Kurt Roeckx
On Sat, Jan 12, 2019 at 05:06:18PM -0800, Jim Wilson wrote: > On Sat, Jan 12, 2019 at 3:21 PM Kurt Roeckx wrote: > > > But how many are actually used? Which does Debian support? > > > > I'm not at all an export of mips, I really don't know that much > > about it. > > It depends on how you count A

Re: RISC-V support

2019-01-12 Thread Jim Wilson
On Sat, Jan 12, 2019 at 3:21 PM Kurt Roeckx wrote: > > But how many are actually used? Which does Debian support? > > I'm not at all an export of mips, I really don't know that much > about it. It depends on how you count ABIs, but yes there have unfortunately been a lot of them over the years.

Re: [PATCH] RISC-V: Add untested 32-bit core file support.

2019-01-12 Thread Jim Wilson
On Sat, Jan 12, 2019 at 2:29 PM Mark Wielaard wrote: > I don't really like adding code that cannot be tested. But it does look > the 32-bit port isn't far off, just waiting for the next linux/glibc > release to settle the time_t ABI. And the code does look correct. > Except for... We don't expect

Re: RISC-V support

2019-01-12 Thread Kurt Roeckx
On Sat, Jan 12, 2019 at 11:35:48PM +0100, Mark Wielaard wrote: > On Sat, 2019-01-12 at 00:23 +0100, Kurt Roeckx wrote: > > I've been looking at mips, and it seems to have many different > > ABIs too. A patch I've received does this: > > int > > mips_return_value_location (Dwarf_Die *functypedie, co

Re: RISC-V support

2019-01-12 Thread Mark Wielaard
On Sat, 2019-01-12 at 00:23 +0100, Kurt Roeckx wrote: > I've been looking at mips, and it seems to have many different > ABIs too. A patch I've received does this: > int > mips_return_value_location (Dwarf_Die *functypedie, const Dwarf_Op > **locp) > { > /* First find the ABI used by the elf obje

Re: [PATCH] RISC-V: Add untested 32-bit core file support.

2019-01-12 Thread Mark Wielaard
On Thu, 2018-12-27 at 15:27 -0800, Jim Wilson wrote: > This conflicts with the previoues two patches. Adds 32-bit support exactly > the > same way that the sparc backend handles 32- and 64-bit core file support. The > 64-bit core file support was tested and still works same as before. I don't r

[Bug libelf/24089] A Heap-buffer-overflow problem was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf

2019-01-12 Thread wcventure at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24089 --- Comment #1 from wcventure --- Created attachment 11535 --> https://sourceware.org/bugzilla/attachment.cgi?id=11535&action=edit POC2 -- You are receiving this mail because: You are on the CC list for the bug.

[Bug libelf/24089] New: A Heap-buffer-overflow problem was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf

2019-01-12 Thread wcventure at 126 dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24089 Bug ID: 24089 Summary: A Heap-buffer-overflow problem was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf Product: elfutils Version: unspecified