This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Program received signal SIG33, Real-time event 33.


On 9/2/07, Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
> Daniel Jacobowitz wrote:
> > On Sun, Sep 02, 2007 at 12:50:46AM -0700, Petr Vandrovec wrote:
> >> Apparently your program uses signals...  If this is expected (which probably is
> >> for realtime signals) then
> >>
> >> handle SIG33 nostop noprint pass
> >>
> >> will configure gdb so this signal is ignored by gdb, but delivered to program
> >> like without gdb.
> >
> > No, SIG33 is generally internal to the threading implementation.
> >
> > GDB 6.3 is somewhat old.  I recommend trying a current version.
>
> If Ying uses setuid() from multithreaded program then I think that glibc
> has more than one surprise ready for him...
>                                                                 Petr
>

I am trying to run Darwin (apple's open source streaming server) in
gdb on Fedora 5.  I am not sure if it uses setuid().

What should I do? upgrade to newer gdb? or glibc?
>
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]