problem with "info spu signal" command on spu-gdb
Ulrich Weigand
uweigand@de.ibm.com
Mon Mar 3 14:28:00 GMT 2008
Hello Takano-san,
> This problem is caused by what the GDB's internal function "strtoulst()" expects
> the entry of SPUFS should have the LF code (0x0a) and null (0x00) in its end.
> The only signal_type doesn't have it.
> (event_status and event_mask are OK)
>
> In order to fix this problem, of course, it is possible to modify the SPUFS.
> Tentatively I would like GDB to work around it.
Thanks for reporting this problem. I agree that GDB should not rely
on a null terminator being present when reading spufs files, so your
patch should go in.
Could you provide a ChangeLog entry describing the patch?
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
More information about the Gdb-patches
mailing list