public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* RE: [ECOS] Startup problem
@ 2004-06-10 18:28 Rycerz Roman-G11565
  0 siblings, 0 replies; 7+ messages in thread
From: Rycerz Roman-G11565 @ 2004-06-10 18:28 UTC (permalink / raw)
  To: ecos-discuss

I have tried running and re-running the same binary..... Same results ran a memcheck program and it checks out ok.
I have increased my stack to 32k, and already removed the -O2 option


Roman


-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com] 
Sent: Thursday, June 10, 2004 11:01 AM
To: Rycerz Roman-G11565
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Startup problem


On Thu, 2004-06-10 at 09:49, Rycerz Roman-G11565 wrote:
> Sorry I keep forgetting to include the environments
> 
>   * What target platform [processor architecture] -> Power PC  on a MPC5554
>   * What tools are you using				  -> gcc 2.95.3-10, Insight 5.2, ecos config tool 2.11
>   * What eCos configuration 				  -> I/O subsystem, Serial Device Drivers, eCos Kernel
>   * Is this repeatable or random			  -> random in the sense that from 1 compile to the next it comes and goes
> 

What about rerunning the same binary?  If it fails, does it always fail, or only sometimes?  If it's the latter, I'd suspect a RAM problem. If it always fails, then it may be a compiler issue.

> 
> Roman
> 
> 
> 
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Sent: Thursday, June 10, 2004 10:33 AM
> To: Sven Rehfuss
> Cc: Rycerz Roman-G11565; ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] Startup problem
> 
> 
> On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> > Hi,
> > use a debugger and check the code. If the routines modify stack
> > variables before decrementing the stack pointer, it maybe is the same 
> > problem I had. If it is the same problem, I can give you the solution.
> 
> Why not share this solution with us all?  After all, that's what this 
> forum is for!
> 
> > 
> > Regards,
> >  Sven Rehfu?
> > 
> > 
> > Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > > Hi
> > >  
> > > I have an intermittent problem.  When starting up the eCos kernel
> > > the call to "cyg_hal_invoke_constructors" sometimes fails with a 
> > > segmentation violation. It seems to happening when the destructors 
> > > are being called. in thread.cxx
> > >  
> > > its in the routine "~cyg_thread_remove_from_list", it seem to be
> > > working it way back thru a linked list assigning
> > > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
> > >  
> > > I know this is a quite vague description, and I may all wrong.. 
> > > But
> > > does anyone have any ideas why this is happening ???
> 
> You've not told us much about your environment.  
>   * What target platform [processor architecture]?
>   * What tools are you using
>   * What eCos configuration 
>   * Is this repeatable or random
> 
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: [ECOS] Startup problem
  2004-06-10 15:49 Rycerz Roman-G11565
@ 2004-06-10 16:01 ` Gary Thomas
  0 siblings, 0 replies; 7+ messages in thread
From: Gary Thomas @ 2004-06-10 16:01 UTC (permalink / raw)
  To: Rycerz Roman-G11565; +Cc: ecos-discuss

On Thu, 2004-06-10 at 09:49, Rycerz Roman-G11565 wrote:
> Sorry I keep forgetting to include the environments
> 
>   * What target platform [processor architecture] -> Power PC  on a MPC5554
>   * What tools are you using				  -> gcc 2.95.3-10, Insight 5.2, ecos config tool 2.11
>   * What eCos configuration 				  -> I/O subsystem, Serial Device Drivers, eCos Kernel
>   * Is this repeatable or random			  -> random in the sense that from 1 compile to the next it comes and goes
> 

What about rerunning the same binary?  If it fails, does it always fail,
or only sometimes?  If it's the latter, I'd suspect a RAM problem.
If it always fails, then it may be a compiler issue.

> 
> Roman
> 
> 
> 
> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com] 
> Sent: Thursday, June 10, 2004 10:33 AM
> To: Sven Rehfuss
> Cc: Rycerz Roman-G11565; ecos-discuss@sources.redhat.com
> Subject: Re: [ECOS] Startup problem
> 
> 
> On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> > Hi,
> > use a debugger and check the code. If the routines modify stack 
> > variables before decrementing the stack pointer, it maybe is the same 
> > problem I had. If it is the same problem, I can give you the solution.
> 
> Why not share this solution with us all?  After all, that's what this forum is for!
> 
> > 
> > Regards,
> >  Sven Rehfu?
> > 
> > 
> > Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > > Hi
> > >  
> > > I have an intermittent problem.  When starting up the eCos kernel 
> > > the call to "cyg_hal_invoke_constructors" sometimes fails with a 
> > > segmentation violation. It seems to happening when the destructors 
> > > are being called. in thread.cxx
> > >  
> > > its in the routine "~cyg_thread_remove_from_list", it seem to be 
> > > working it way back thru a linked list assigning
> > > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
> > >  
> > > I know this is a quite vague description, and I may all wrong.. But 
> > > does anyone have any ideas why this is happening ???
> 
> You've not told us much about your environment.  
>   * What target platform [processor architecture]?
>   * What tools are you using
>   * What eCos configuration 
>   * Is this repeatable or random
> 
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: [ECOS] Startup problem
@ 2004-06-10 15:49 Rycerz Roman-G11565
  2004-06-10 16:01 ` Gary Thomas
  0 siblings, 1 reply; 7+ messages in thread
From: Rycerz Roman-G11565 @ 2004-06-10 15:49 UTC (permalink / raw)
  To: ecos-discuss

Sorry I keep forgetting to include the environments

  * What target platform [processor architecture] -> Power PC  on a MPC5554
  * What tools are you using				  -> gcc 2.95.3-10, Insight 5.2, ecos config tool 2.11
  * What eCos configuration 				  -> I/O subsystem, Serial Device Drivers, eCos Kernel
  * Is this repeatable or random			  -> random in the sense that from 1 compile to the next it comes and goes


Roman



-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com] 
Sent: Thursday, June 10, 2004 10:33 AM
To: Sven Rehfuss
Cc: Rycerz Roman-G11565; ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Startup problem


On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> Hi,
> use a debugger and check the code. If the routines modify stack 
> variables before decrementing the stack pointer, it maybe is the same 
> problem I had. If it is the same problem, I can give you the solution.

Why not share this solution with us all?  After all, that's what this forum is for!

> 
> Regards,
>  Sven Rehfu?
> 
> 
> Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > Hi
> >  
> > I have an intermittent problem.  When starting up the eCos kernel 
> > the call to "cyg_hal_invoke_constructors" sometimes fails with a 
> > segmentation violation. It seems to happening when the destructors 
> > are being called. in thread.cxx
> >  
> > its in the routine "~cyg_thread_remove_from_list", it seem to be 
> > working it way back thru a linked list assigning
> > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
> >  
> > I know this is a quite vague description, and I may all wrong.. But 
> > does anyone have any ideas why this is happening ???

You've not told us much about your environment.  
  * What target platform [processor architecture]?
  * What tools are you using
  * What eCos configuration 
  * Is this repeatable or random

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Startup problem
  2004-06-10 15:33   ` Gary Thomas
@ 2004-06-10 15:39     ` Sven Rehfuss
  0 siblings, 0 replies; 7+ messages in thread
From: Sven Rehfuss @ 2004-06-10 15:39 UTC (permalink / raw)
  To: Gary Thomas; +Cc: ecos-discuss

Hi,
I posted my solution before (solution - thumb/exceptions) and do not
want to repeat.

Regards,
 Sven Rehfuß

Am Do, den 10.06.2004 schrieb Gary Thomas um 17:33:
> On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> > Hi,
> > use a debugger and check the code. If the routines modify stack
> > variables before decrementing the stack pointer, it maybe is the same
> > problem I had.
> > If it is the same problem, I can give you the solution.
> 
> Why not share this solution with us all?  After all, that's what this
> forum is for!
> 
> > 
> > Regards,
> >  Sven Rehfuß
> > 
> > 
> > Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > > Hi
> > >  
> > > I have an intermittent problem.  When starting up the eCos kernel the call to "cyg_hal_invoke_constructors" sometimes fails with a segmentation violation.
> > > It seems to happening when the destructors are being called.
> > > in thread.cxx
> > >  
> > > its in the routine "~cyg_thread_remove_from_list", it seem to be working it way back thru a linked list assigning 
> > > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
> > >  
> > > I know this is a quite vague description, and I may all wrong..
> > > But does anyone have any ideas why this is happening ???
> 
> You've not told us much about your environment.  
>   * What target platform [processor architecture]?
>   * What tools are you using
>   * What eCos configuration 
>   * Is this repeatable or random
-- 
B2motion GmbH
Sven Rehfuß
Projekt/System Engineer

Otto-Lilienthal Straße 29
D-28199 Bremen
Tel.: +49 421 24111 - 22
Fax : +49 421 24111 - 99
Mobil: +49 179 7058740
Email: sven.rehfuss@b2motion.de


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Startup problem
  2004-06-10 15:22 ` Sven Rehfuss
@ 2004-06-10 15:33   ` Gary Thomas
  2004-06-10 15:39     ` Sven Rehfuss
  0 siblings, 1 reply; 7+ messages in thread
From: Gary Thomas @ 2004-06-10 15:33 UTC (permalink / raw)
  To: Sven Rehfuss; +Cc: Rycerz Roman-G11565, ecos-discuss

On Thu, 2004-06-10 at 09:23, Sven Rehfuss wrote:
> Hi,
> use a debugger and check the code. If the routines modify stack
> variables before decrementing the stack pointer, it maybe is the same
> problem I had.
> If it is the same problem, I can give you the solution.

Why not share this solution with us all?  After all, that's what this
forum is for!

> 
> Regards,
>  Sven Rehfuß
> 
> 
> Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> > Hi
> >  
> > I have an intermittent problem.  When starting up the eCos kernel the call to "cyg_hal_invoke_constructors" sometimes fails with a segmentation violation.
> > It seems to happening when the destructors are being called.
> > in thread.cxx
> >  
> > its in the routine "~cyg_thread_remove_from_list", it seem to be working it way back thru a linked list assigning 
> > prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
> >  
> > I know this is a quite vague description, and I may all wrong..
> > But does anyone have any ideas why this is happening ???

You've not told us much about your environment.  
  * What target platform [processor architecture]?
  * What tools are you using
  * What eCos configuration 
  * Is this repeatable or random

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [ECOS] Startup problem
  2004-06-10 15:08 Rycerz Roman-G11565
@ 2004-06-10 15:22 ` Sven Rehfuss
  2004-06-10 15:33   ` Gary Thomas
  0 siblings, 1 reply; 7+ messages in thread
From: Sven Rehfuss @ 2004-06-10 15:22 UTC (permalink / raw)
  To: Rycerz Roman-G11565; +Cc: ecos-discuss

Hi,
use a debugger and check the code. If the routines modify stack
variables before decrementing the stack pointer, it maybe is the same
problem I had.
If it is the same problem, I can give you the solution.

Regards,
 Sven Rehfuß


Am Do, den 10.06.2004 schrieb Rycerz Roman-G11565 um 17:08:
> Hi
>  
> I have an intermittent problem.  When starting up the eCos kernel the call to "cyg_hal_invoke_constructors" sometimes fails with a segmentation violation.
> It seems to happening when the destructors are being called.
> in thread.cxx
>  
> its in the routine "~cyg_thread_remove_from_list", it seem to be working it way back thru a linked list assigning 
> prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
>  
> I know this is a quite vague description, and I may all wrong..
> But does anyone have any ideas why this is happening ???
>  
> thanks
> roman
>  
-- 
B2motion GmbH
Sven Rehfuß
Projekt/System Engineer

Otto-Lilienthal Straße 29
D-28199 Bremen
Tel.: +49 421 24111 - 22
Fax : +49 421 24111 - 99
Mobil: +49 179 7058740
Email: sven.rehfuss@b2motion.de


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [ECOS] Startup problem
@ 2004-06-10 15:08 Rycerz Roman-G11565
  2004-06-10 15:22 ` Sven Rehfuss
  0 siblings, 1 reply; 7+ messages in thread
From: Rycerz Roman-G11565 @ 2004-06-10 15:08 UTC (permalink / raw)
  To: 'ecos-discuss@sources.redhat.com'

Hi
 
I have an intermittent problem.  When starting up the eCos kernel the call to "cyg_hal_invoke_constructors" sometimes fails with a segmentation violation.
It seems to happening when the destructors are being called.
in thread.cxx
 
its in the routine "~cyg_thread_remove_from_list", it seem to be working it way back thru a linked list assigning 
prev = prev->list_next when it blows up prev is set to the contents of memory "0", location  a null ptr problem.
 
I know this is a quite vague description, and I may all wrong..
But does anyone have any ideas why this is happening ???
 
thanks
roman
 
 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2004-06-10 18:28 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-06-10 18:28 [ECOS] Startup problem Rycerz Roman-G11565
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 15:49 Rycerz Roman-G11565
2004-06-10 16:01 ` Gary Thomas
2004-06-10 15:08 Rycerz Roman-G11565
2004-06-10 15:22 ` Sven Rehfuss
2004-06-10 15:33   ` Gary Thomas
2004-06-10 15:39     ` Sven Rehfuss

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).