Darn, I was hoping that would be a smoking gun. We have three Orca
developers (Rich, Mike, and Joanie) testing on Feisty, and they cannot
seem to reproduce the problem. I'm still curious if this might be
related to specific multibyte characters.
Are you running some sort of application in gnome-
Hi.
It is en_US.UTF-8.
Kenny
On Wed, Jan 10, 2007 at 11:43:02AM -0500, Willie Walker wrote:
> Hi Kenny:
>
> Which locale are you using? Is it en_US or something else?
>
> Will
>
> On Wed, 2007-01-10 at 07:01 -0600, Kenny Hitt wrote:
> > Hi.
> >
> >
> > On Wed, Jan 10, 2007 at 08:
Hi Kenny:
Which locale are you using? Is it en_US or something else?
Will
On Wed, 2007-01-10 at 07:01 -0600, Kenny Hitt wrote:
> Hi.
>
>
> On Wed, Jan 10, 2007 at 08:10:56AM +, Padraig O'Briain wrote:
> > #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135
> >
> > This show
Hi.
On Wed, Jan 10, 2007 at 08:10:56AM +, Padraig O'Briain wrote:
> #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135
>
> This shows that the number of bytes is wrong.
>
> I suggest logging a bug againt vte.
>
> I would be helpful if we knew what the text was.
>
>
It's ha
I had a quick look at the code and it is calculating character offsets.
One possibility is that 560 or 561 is in the middle of a character.
Li Yuan wrote:
> Yes, I think it is vte's problem.
>
> I saw (start_offset=560, end_offset=561). It is strange, end-start
> should be a reasonable positive v
Yes, I think it is vte's problem.
I saw (start_offset=560, end_offset=561). It is strange, end-start
should be a reasonable positive value, not that big (4294967257).
Li
On Wed, 2007-01-10 at 08:10 +, Padraig O'Briain wrote:
> #8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135
#8 0xb7677249 in IA__g_malloc (n_bytes=4294967257) at gmem.c:135
This shows that the number of bytes is wrong.
I suggest logging a bug againt vte.
I would be helpful if we knew what the text was.
Kenny Hitt wrote:
> Replying to myself since I deleted the other messages in the thread.
>
> I us
