home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!ucbvax!mtxinu!sybase!cosmo!davidvc
- From: davidvc@cosmo.sybase.com (David Van Couvering)
- Newsgroups: comp.databases.sybase
- Subject: Re: Open Server message Q problem
- Message-ID: <25500@sybase.sybase.com>
- Date: 6 Nov 92 19:28:24 GMT
- References: <BwswD0.1MF@da_vinci.it.uswc.uswest.com>
- Sender: news@Sybase.COM
- Distribution: na
- Lines: 29
-
- In article <BwswD0.1MF@da_vinci.it.uswc.uswest.com>, twood@windward.it.uswc.uswest.com (Tim Woodward) writes:
- |>
- |>
- |> Anyone out there with experience using message queues in the Open
- |> Server version 2?
- [deleted]
- |>
- |> ex: if (srv_putmsgq(log_service, log_request, SRV_M_NOWAIT) != SUCCEED)
- |>
- |> This causes the error messge that the message logging process has corrupted
- |> or overflowed its stack and the program exits.
- |>
- |> ex: Fatal Oserver error: 16151:20:0: Server process '4' has overflowed or
- |> corrupted its stack -- aborting.
- |>
-
- I would make sure that your message queue has been properly allocated
- and you are passing in the pointers correctly -- the stack problem
- usually is a result of memory being overwritten.
-
- |>
- |> Tim Woodward
-
- David
-
- --
- davidvc@sybase.com | {pacbell,lll-tis,pyramid,sun}!sybase!davidvc
- David Van Couvering Sybase 1650 65th Street Emeryville, CA 94608
- - Opinions expressed here are mine and not necessarily those of Sybase -
-