Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: sjackman@gmail.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: sim/arm/armos.c: IsTTY [PATCH]
Date: Thu, 08 Sep 2005 09:07:00 -0000	[thread overview]
Message-ID: <1126170388.18092.16.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <7f45d93905090709516f912861@mail.gmail.com>

On Wed, 2005-09-07 at 17:51, Shaun Jackman wrote:
> 2005/8/29, Daniel Jacobowitz <drow@false.org>:
> > Please no buffer overflows be adding.  Also, there's plenty of ways to
> > write this without the ugly empty loop body...
> 
> I fixed the potential buffer overflow and cleaned up the loop coding
> style. Thanks for the tips.
> 
> Cheers,
> Shaun
> 
> 2005-09-07  Shaun Jackman  <sjackman@gmail.com>
> 
> 	* sim/arm/armos.c (unlink): Remove this macro. It is unused
> 	in this file and conflicts with sim_callback->unlink.
> 	(SWIopen): Fix a potential buffer overflow.
> 	(SWIremove): New function.
> 	(SWIrename): Ditto.
> 	(ARMul_OSHandleSWI): Handle the RDP calls SWI_IsTTY,
> 	SWI_Remove, and SWI_Rename, as well as the RDI calls
> 	AngelSWI_Reason_IsTTY, AngelSWI_Reason_Remove, and
> 	AngelSWI_Reason_Rename.
> 

Two problems I can immediately see with this.

1) PATH_MAX isn't ANSI (it's POSIX, or something like that).  So you
can't rely on it being defined.  I think for this case you can probably
just define it to 1024 anyway if it's missing, but see
libiberty/lrealpath.c if you want the gory details.

2) If you do overflow the path limit, you need to set the simulator's
errno value and return.  Use cb_host_to_target_errno(sim_callback,
ENAMETOOLONG) to set it.

R.


  reply	other threads:[~2005-09-08  9:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 21:19 Shaun Jackman
2005-08-22 18:51 ` Shaun Jackman
2005-08-30  2:38 ` Daniel Jacobowitz
2005-09-06 16:22   ` Richard Earnshaw
2005-09-07 16:51   ` Shaun Jackman
2005-09-08  9:07     ` Richard Earnshaw [this message]
2005-09-08 19:28       ` Eli Zaretskii
2005-09-09 17:16       ` Shaun Jackman
2005-09-09 17:23       ` Shaun Jackman
2005-09-17 22:37         ` Daniel Jacobowitz
2005-09-17 23:32           ` Shaun Jackman
2005-09-18  1:14             ` Daniel Jacobowitz
2005-09-18  2:40               ` Shaun Jackman
2005-09-18  2:59                 ` Daniel Jacobowitz
     [not found]                 ` <20050918025653.GA4285@nevyn.them.org>
     [not found]                   ` <7f45d93905091720161f61e995@mail.gmail.com>
     [not found]                     ` <20050918033152.GA6546@nevyn.them.org>
2005-10-13 20:30                       ` Shaun Jackman
2005-10-19 16:12                 ` Shaun Jackman
2005-11-17 10:49                   ` Daniel Jacobowitz
2005-11-17 15:54                     ` Shaun Jackman
2005-09-18  3:32           ` Eli Zaretskii
2005-09-18  3:44             ` Daniel Jacobowitz
2005-09-18  9:04               ` Mark Kettenis
2005-09-18 19:13                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1126170388.18092.16.camel@pc960.cambridge.arm.com \
    --to=rearnsha@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sjackman@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox