Sparc64 needs a register profile

[XVilka]

15:19 < vext01> p/debug_native.c: In function 'r_debug_native_continue':
15:19 < vext01> p/debug_native.c:303: warning: cast from pointer to integer of different size
15:19 < vext01> p/debug_native.c:796:2: warning: #warning NO DEBUGGER REGISTERS PROFILE DEFINED
15:19 < vext01> p/debug_native.c: In function 'r_debug_native_reg_read':

Reply 1: I have no access to any sparc64 box, i should think that you are testing in OpenBSD. Ping me by irc if you need some help to cook this patch.

[radare]

@vext01 i guess this may help http://www.openbsd.org/cgi-bin/cvsweb/src/sys/arch/sparc64/include/reg.h?rev=1.5 but i have no sparc64 box to test, so if you are still interested would you mind to share a qemu img or ssh to test this?

thanks

[XVilka]

Any update on this bug on current radare2?

[radare]

Nobody seems interested on sparc64 platform nowadays. Thats not a complex task, but it requires some time to setup the vm and read an include file to write that profile. Not sure if we should fix or just close that issue :) as long as we have more prioritary tasks to do..

On Oct 29, 2013, at 23:27, Anton Kochkov notifications@github.com wrote:

Any update on this bug on current radare2?

—
Reply to this email directly or view it on GitHub.

[jvoisin]

Let's close it.

[radare]

Why?

On 14 Aug 2014, at 23:03, jvoisin notifications@github.com wrote:

Let's close it.

—
Reply to this email directly or view it on GitHub.

[jvoisin]

Because you said:

Not sure if we should fix or just close that issue :) as long as we have more prioritary tasks to do..

[radare]

Now that we use milestones and tags properly it should be fine to keep this bug open until someone with access to an sparc box could test this (i currently dont have access to it, but i could setup a qemu for testing, but didnt do it because we have other issues more prioritary :)

On 14 Aug 2014, at 23:43, jvoisin notifications@github.com wrote:

Because you said:

Not sure if we should fix or just close that issue :) as long as we have more prioritary tasks to do..

—
Reply to this email directly or view it on GitHub.

[deeso]

I think have a sparc box in storage. I can pull it out and check later.
Won't be able to turn it on for a while.
On Aug 15, 2014 6:46 AM, "radare" notifications@github.com wrote:

Now that we use milestones and tags properly it should be fine to keep
this bug open until someone with access to an sparc box could test this (i
currently dont have access to it, but i could setup a qemu for testing, but
didnt do it because we have other issues more prioritary :)

On 14 Aug 2014, at 23:43, jvoisin notifications@github.com wrote:

Because you said:

Not sure if we should fix or just close that issue :) as long as we have
more prioritary tasks to do..

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#27 (comment).

[radare]

This can be done with just having the ptrace.h of this platform from glibc :p but it would be nice to test it before commiting

On 15 Aug 2014, at 13:53, dso notifications@github.com wrote:

I think have a sparc box in storage. I can pull it out and check later.
Won't be able to turn it on for a while.
On Aug 15, 2014 6:46 AM, "radare" notifications@github.com wrote:

Now that we use milestones and tags properly it should be fine to keep
this bug open until someone with access to an sparc box could test this (i
currently dont have access to it, but i could setup a qemu for testing, but
didnt do it because we have other issues more prioritary :)

On 14 Aug 2014, at 23:43, jvoisin notifications@github.com wrote:

Because you said:

Not sure if we should fix or just close that issue :) as long as we have
more prioritary tasks to do..

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#27 (comment).

—
Reply to this email directly or view it on GitHub.