public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* FW: SIGSEGV occurring when code compiled with gcc with multithreaded code.
@ 2000-08-09 11:52 Orlando Betancourt
  0 siblings, 0 replies; 3+ messages in thread
From: Orlando Betancourt @ 2000-08-09 11:52 UTC (permalink / raw)
  To: gcc-bugs

Yes, the compiler was built with the --enable threads flag.  The problem
also occurs in
a Intel based pc system running Solaris.:

SunOS  5.7 Generic i86pc i386 i86

All checks were made to ensure that the compilers on both platforms were
built with the correct flags.

Orlando

-----Original Message-----
From: aoliva@guarana.lsd.ic.unicamp.br
[ mailto:aoliva@guarana.lsd.ic.unicamp.br]On Behalf Of Alexandre Oliva
Sent: Wednesday, August 09, 2000 2:36 PM
To: Orlando Betancourt
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: SIGSEGV occurring when code compiled with gcc with
multithreaded code.


On Aug  9, 2000, "Orlando Betancourt" <orlando.betancourt@solipsys.com>
wrote:

> I get a SIGSEGV violation when executing the following multithreaded code
> after two to three minutes.

Did you build GCC with --enable-threads?

--
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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

* Re: FW: SIGSEGV occurring when code compiled with gcc with multithreaded code.
  2000-08-10  7:02 Orlando Betancourt
@ 2000-08-10 11:49 ` Alexandre Oliva
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Oliva @ 2000-08-10 11:49 UTC (permalink / raw)
  To: Orlando Betancourt; +Cc: gcc-bugs

On Aug 10, 2000, "Orlando Betancourt" <orlando.betancourt@solipsys.com> wrote:

> Using the flag solved the problem.

Now guess what?  The -pthreads flag, which is supposed to be used when
compiling and linking multi-threaded code, not only links with
-lpthread, but also -Defines _REENTRANT and _PTHREADS :-)

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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

* FW: SIGSEGV occurring when code compiled with gcc with multithreaded code.
@ 2000-08-10  7:02 Orlando Betancourt
  2000-08-10 11:49 ` Alexandre Oliva
  0 siblings, 1 reply; 3+ messages in thread
From: Orlando Betancourt @ 2000-08-10  7:02 UTC (permalink / raw)
  To: gcc-bugs

Using the flag solved the problem.

Thanks,

Orlando M. Betancourt

-----Original Message-----
From: aoliva@guarana.lsd.ic.unicamp.br
[ mailto:aoliva@guarana.lsd.ic.unicamp.br]On Behalf Of Alexandre Oliva
Sent: Wednesday, August 09, 2000 3:09 PM
To: Orlando Betancourt
Subject: Re: SIGSEGV occurring when code compiled with gcc with
multithreaded code.


On Aug  9, 2000, "Orlando Betancourt" <orlando.betancourt@solipsys.com>
wrote:

> Yes, the compiler was built with the --enable threads flag.  The
> problem also occurs in a Intel based pc system running Solaris.:

A wild guess: try to compile with -D_PTHREADS

--
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


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

end of thread, other threads:[~2000-08-10 11:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-08-09 11:52 FW: SIGSEGV occurring when code compiled with gcc with multithreaded code Orlando Betancourt
2000-08-10  7:02 Orlando Betancourt
2000-08-10 11:49 ` Alexandre Oliva

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).