Re: [Cegcc-devel] problem in prologue and environ

2008-10-04 Thread Pawel Veselov
Hi, here is the modified patch, hope I got everything :) Thanks, Pawel. On Sat, Sep 20, 2008 at 3:27 PM, Pedro Alves <[EMAIL PROTECTED]> wrote: > On Saturday 20 September 2008 22:37:40, Pawel Veselov wrote: >> [ skipped ] Index: src/newlib/newlib/libc/sys/wince/sys/shared.h ==

Re: [Cegcc-devel] problem in prologue and environ

2008-10-04 Thread Pedro Alves
Patch checked in. Haven't tested it, but I trust you have. ;-) Thanks, -- Pedro Alves - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin S

Re: [Cegcc-devel] problem in prologue and environ

2008-09-20 Thread Pedro Alves
On Saturday 20 September 2008 22:37:40, Pawel Veselov wrote: > > I'll change the patch to conform. Yet I hope you don't mind me > replying to the comments :) Not at all! > > >> 7.diff > >> Index: newlib/libc/stdlib/setenv_r.c > >>

Re: [Cegcc-devel] problem in prologue and environ

2008-09-20 Thread Pedro Alves
On Saturday 20 September 2008 22:37:40, Pawel Veselov wrote: > > I'll change the patch to conform. Yet I hope you don't mind me > replying to the comments :) Not at all! > > >> 7.diff > >> Index: newlib/libc/stdlib/setenv_r.c > >>

Re: [Cegcc-devel] problem in prologue and environ

2008-09-20 Thread Pawel Veselov
> Comments below. Please excuse my nit-pickiness. :-) >> --- newlib/libc/sys/wince/sys/shared.h (revision 1182) >> +++ newlib/libc/sys/wince/sys/shared.h (working copy) >> @@ -30,10 +30,14 @@ >> >> _SHMBLK _shared_init(int pgid); >> void_shared_dump(_SHMBLK shmblk); >> -int_shared_get

Re: [Cegcc-devel] problem in prologue and environ

2008-09-20 Thread Pawel Veselov
Hi Pedro! On Sat, Sep 20, 2008 at 8:47 AM, Pedro Alves <[EMAIL PROTECTED]> wrote: > Hi Pawel. Thanks for fixing this! > Comments below. Please excuse my nit-pickiness. :-) I'll change the patch to conform. Yet I hope you don't mind me replying to the comments :) >> 7.diff >> Index: newlib/l

Re: [Cegcc-devel] problem in prologue and environ

2008-09-20 Thread Pedro Alves
Hi Pawel. Thanks for fixing this! Comments below. Please excuse my nit-pickiness. :-) On Friday 19 September 2008 00:31:11, Pawel Veselov wrote: > -- > With best of best regards > Pawel S. Veselov > 7.diff > Index: newlib/libc/stdlib/setenv_r.c > =

Re: [Cegcc-devel] problem in prologue and environ

2008-09-18 Thread Pawel Veselov
And, the patch ! :) On Thu, Sep 18, 2008 at 4:29 PM, Pawel Veselov <[EMAIL PROTECTED]> wrote: > Hi! > > I'm attaching the patch that allegedly takes care of these problems. > The main changes are: > > - prevent initializing the environment variables from the shared block twice > - fix the initiali

Re: [Cegcc-devel] problem in prologue and environ

2008-09-18 Thread Pawel Veselov
Hi! I'm attaching the patch that allegedly takes care of these problems. The main changes are: - prevent initializing the environment variables from the shared block twice - fix the initialization of the environment variables from the shared block - change the function names in shared.c to match

Re: [Cegcc-devel] problem in prologue and environ

2008-09-17 Thread Pawel Veselov
Hi, On Wed, Sep 17, 2008 at 7:46 PM, Pedro Alves <[EMAIL PROTECTED]> wrote: > On Thursday 18 September 2008 02:56:47, Pawel Veselov wrote: >> Argh, took me a find out what's going on. Will need some more time to >> actually produce a fix. Discovered all that while testing the changes >> to the tra

Re: [Cegcc-devel] problem in prologue and environ

2008-09-17 Thread Pedro Alves
On Thursday 18 September 2008 02:56:47, Pawel Veselov wrote: > Argh, took me a find out what's going on. Will need some more time to > actually produce a fix. Discovered all that while testing the changes > to the tracer. AFAIK, you should be able to debug cegcc.dll with gdbserver, cuz gdbserver.e

[Cegcc-devel] problem in prologue and environ

2008-09-17 Thread Pawel Veselov
Argh, took me a find out what's going on. Will need some more time to actually produce a fix. Discovered all that while testing the changes to the tracer. The application has a good chance crashing in prologue, if it's being attached to an existing process group. I guess those are the reasons I fo