From david.sauvage at adalabs.com Fri Feb 3 10:21:37 2012 From: david.sauvage at adalabs.com (David SAUVAGE - AdaLabs Ltd) Date: Fri, 03 Feb 2012 13:21:37 +0400 Subject: [AWS] AWS GPL 2011 / Random Tasking_Error (aws-utils.adb:759) on applicatoin launch In-Reply-To: <4F19C237.6090106@adalabs.com> References: <4EF334AA.9070404@adalabs.com> <4EF34CEF.6010302@obry.net> <4F19BB89.7030706@adalabs.com> <4F19C237.6090106@adalabs.com> Message-ID: <4F2BA721.9080904@adalabs.com> Dear Pascal, finally I got it, it as nothing to do with AWS. The project use some high level components built using gprbuild, and other low level components build using gnatmake. Depending on what components are built first the issue happen... I am using only gnatmake to build all components and the issue do not happen anymore. Sorry for the spam. Cheers, David SAUVAGE Software Agile Architect, Director AdaLabs Ltd - Mauritius http://adalabs.com +230 428 18 32 skype sauvaged BRN C10097052 VAT 27035043 Le 20/01/2012 23:36, David SAUVAGE - AdaLabs Ltd a ?crit : > Pascal, > > it is not at elaboration, but during the first lines of my application > execution, here is the calls before the SIGSEGV: > > 1. [application code] AWS.Log.Write (Log_Object, S); > 2. [aws-log.adb:492] Write_Log ... > 3. system.tasking.protected_objects.operation.protected_entry_call > 4. system.tasking.protected_objects.operation.po_do_or_queue > => SIGSEGV, Segmentation fault. > > > AWS.Log.Start (Log_Object, ...); as been called before the > AWS.Log.Write (Log_Object, S); > Is there any other conditions to ensure before using a data of type > AWS.Log.Object declared at library level ? > > I replaced the AWS.Log.Write call with Ada.Text_IO.Put_Line and the > issue did not occur. > > This issue is not systematic. It can stop occurring after recompilation > or re-run. > > Cheers, > > > David SAUVAGE > > Software Agile Architect, Director > AdaLabs Ltd - Mauritius > http://adalabs.com > +230 428 18 32 > skype sauvaged > BRN C10097052 > VAT 27035043 > > > Le 20/01/2012 23:07, David SAUVAGE - AdaLabs Ltd a ?crit : >> Pascal, >> >> Le 22/12/2011 19:29, Pascal Obry a ?crit : >>> Would be nice to have a reproducer indeed. >> The issue is occurring again, >> >> when I debug the application using GPS debug session I got the following >> error (at elaboration) I suppose. >> >> Program received signal SIGSEGV, Segmentation fault. >> 0xb7750373 in system.tasking.protected_objects.operations.po_do_or_queue >> () from >> /lib/gcc/i686-pc-linux-gnu/4.5.3/adalib/libgnarl-2011.so >> >> Currently, I don't know if this is related or not, but it is the first >> time I have this. >> >> any tips on how to proceed is most welcome ... >> >> Cheers, >> >> David SAUVAGE >> >> Software Agile Architect, Director >> AdaLabs Ltd - Mauritius >> http://adalabs.com >> +230 428 18 32 >> skype sauvaged >> BRN C10097052 >> VAT 27035043 >> >> From marius at amado-alves.info Fri Feb 3 12:56:04 2012 From: marius at amado-alves.info (Marius Amado-Alves) Date: Fri, 3 Feb 2012 11:56:04 +0000 Subject: [AWS] AWS GPL 2011 / Random Tasking_Error (aws-utils.adb:759) on applicatoin launch In-Reply-To: <4F2BA721.9080904@adalabs.com> References: <4EF334AA.9070404@adalabs.com> <4EF34CEF.6010302@obry.net> <4F19BB89.7030706@adalabs.com> <4F19C237.6090106@adalabs.com> <4F2BA721.9080904@adalabs.com> Message-ID: > I am using only gnatmake to build all components and the issue do not > happen anymore. > > Sorry for the spam. (David SAUVAGE) This is no spam at all, since you presented a solution to one of the instalation/building problems of AWS. Thanks for sharing. /* I'm hoping on a thread like this eventually solve my problem of not being able to build with SSH on Windows. */ From pascal at obry.net Sat Feb 4 14:39:49 2012 From: pascal at obry.net (Pascal Obry) Date: Sat, 04 Feb 2012 14:39:49 +0100 Subject: [AWS] AWS GPL 2011 / Random Tasking_Error (aws-utils.adb:759) on applicatoin launch In-Reply-To: <4F2BA721.9080904@adalabs.com> References: <4EF334AA.9070404@adalabs.com> <4EF34CEF.6010302@obry.net> <4F19BB89.7030706@adalabs.com> <4F19C237.6090106@adalabs.com> <4F2BA721.9080904@adalabs.com> Message-ID: <4F2D3525.3000304@obry.net> David, > finally I got it, it as nothing to do with AWS. Good to know! > The project use some high level components built using gprbuild, and > other low level components build using gnatmake. > > Depending on what components are built first the issue happen... Really strange! > I am using only gnatmake to build all components and the issue do not > happen anymore. > > Sorry for the spam. Not a spam at all, if others are hitting this issue we now have a solution. Thanks. Pascal. -- --|------------------------------------------------------ --| Pascal Obry Team-Ada Member --| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE --|------------------------------------------------------ --| http://www.obry.net - http://v2p.fr.eu.org --| "The best way to travel is by means of imagination" --| --| gpg --keyserver keys.gnupg.net --recv-key F949BD3B From thomas.granvej6 at gmail.com Thu Feb 9 09:59:47 2012 From: thomas.granvej6 at gmail.com (=?ISO-8859-1?Q?Thomas_L=F8cke?=) Date: Thu, 9 Feb 2012 09:59:47 +0100 Subject: [AWS] The new Too_Many_Parameters exception Message-ID: Hey all, Is the Too_Many_Parameters exception that is raised when a client is sending excessive POST parameters handled internally by AWS, and all we users have to do is keep an eye on the log data, or do I have to add an exception handler for this in every method that make use of POST parameters? I glanced at the code, but I couldn't find a place where the exception was caught, hence the question. :o) Thomas L?cke -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/aws/attachments/20120209/865b08b0/attachment.htm From thomas.granvej6 at gmail.com Thu Feb 9 11:01:01 2012 From: thomas.granvej6 at gmail.com (=?ISO-8859-1?Q?Thomas_L=F8cke?=) Date: Thu, 9 Feb 2012 11:01:01 +0100 Subject: [AWS] The new Too_Many_Parameters exception In-Reply-To: References: Message-ID: On Thu, Feb 9, 2012 at 9:59 AM, Thomas L?cke wrote: > Hey all, > > Is the Too_Many_Parameters exception that is raised when a client is > sending excessive POST parameters handled internally by AWS, and all we > users have to do is keep an eye on the log data, or do I have to add an > exception handler for this in every method that make use of POST parameters? > > I glanced at the code, but I couldn't find a place where the exception was > caught, hence the question. > Never mind the above question. With some help from curl, I've learned that I have to catch this exception myself and do something meaningful with it. All is well. :o) Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/aws/attachments/20120209/d4e2f671/attachment.htm From pascal at obry.net Thu Feb 9 11:01:25 2012 From: pascal at obry.net (Pascal Obry) Date: Thu, 9 Feb 2012 11:01:25 +0100 Subject: [AWS] The new Too_Many_Parameters exception In-Reply-To: References: Message-ID: Thomas, > Is the?Too_Many_Parameters exception?that is raised when a client is sending > excessive POST parameters handled internally by AWS, and all we users have > to do is keep an eye on the log data, or do I have to add an exception > handler for this in every method that make use of POST parameters? There is no way to get this exception at the user level. This is a 500 (Server Error) message and this is what a user will get as a response in the browser. Thinking more about this it is probably better to return a 403 (Forbidden) error code as this is a not a server error at all! Pascal. -- --|------------------------------------------------------ --| Pascal Obry? ? ? ? ? ? ? ? ? ? ? ? ?? Team-Ada Member --| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE --|------------------------------------------------------ --|? ? ? ? ? ? ? http://www.obry.net --| "The best way to travel is by means of imagination" --| --| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595 From thomas.granvej6 at gmail.com Thu Feb 9 11:13:16 2012 From: thomas.granvej6 at gmail.com (=?ISO-8859-1?Q?Thomas_L=F8cke?=) Date: Thu, 9 Feb 2012 11:13:16 +0100 Subject: [AWS] The new Too_Many_Parameters exception In-Reply-To: References: Message-ID: On Thu, Feb 9, 2012 at 11:01 AM, Pascal Obry wrote: > > > There is no way to get this exception at the user level. This is a 500 > (Server Error) > message and this is what a user will get as a response in the browser. > I'm using AWS.Server.Set_Unexpected_Exception_Handler, so issuing a 500 when there are too many POST parameters isn't a big problem. It can be handled. > Thinking more about this it is probably better to return a 403 > (Forbidden) error code > as this is a not a server error at all! Yea, I could see this work also. The user is doing something "bad", and hence he's hit with a forbidden error. There's some solid logic in that. :o) Thomas L?cke -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/aws/attachments/20120209/8216492d/attachment.htm From pascal at obry.net Thu Feb 9 17:05:37 2012 From: pascal at obry.net (Pascal Obry) Date: Thu, 09 Feb 2012 17:05:37 +0100 Subject: [AWS] The new Too_Many_Parameters exception In-Reply-To: References: Message-ID: <4F33EED1.3000707@obry.net> Thomas, > Yea, I could see this work also. The user is doing something "bad", and > hence he's hit with a forbidden error. There's some solid logic in that. Just committed, a 403 error code is now returned. Pascal. -- --|------------------------------------------------------ --| Pascal Obry Team-Ada Member --| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE --|------------------------------------------------------ --| http://www.obry.net - http://v2p.fr.eu.org --| "The best way to travel is by means of imagination" --| --| gpg --keyserver keys.gnupg.net --recv-key F949BD3B