public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Kern Sibbald <kern@sibbald.com>
Cc: cygwin@cygwin.com
Subject: Re: Bug report
Date: Mon, 05 May 2003 16:38:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.44.0305051236270.25128-100000@slinky.cs.nyu.edu> (raw)
In-Reply-To: <1052151684.5361.937.camel@rufus>

On 5 May 2003, Kern Sibbald wrote:

> I guess you guys (and gal) really don't want bug
> reports because it is not at all obvious where
> to send them.

This is the right place.

> Anyway here is one:
>
> Running WinXP Home version.
>
> Using Cygwin 1.3.20
>
> When running my program with LocalSystem userid
> as a service, doing a pthread_kill(thread_id, SIGUSR2)
> causes some sort of memory fault referencing memory at 0x3a
> (or something like that because the program disappears
> poof).
>
> Running as a normal user works fine.

What's the exact error message (I assume you get a popup box)?
Is there a stacktrace file generated?  Did you try setting
"error_start:c:/cygwin/bin/dumper.exe" in your CYGWIN environment
variable?  Did you try running the program from the command line in a
LocalSystem-owned shell?  Can you provide a simple testcase that
reproduces your problem?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-05-05 16:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 16:21 Kern Sibbald
2003-05-05 16:38 ` Igor Pechtchanski [this message]
2003-05-05 17:14   ` Kern Sibbald
2003-05-05 17:30     ` Igor Pechtchanski
2003-05-05 17:33       ` Igor Pechtchanski
2003-05-08 10:52       ` pthread_signal() references illegal memory address Kern Sibbald
2003-05-08 16:09         ` Joshua Daniel Franklin
2003-05-08 19:03         ` Igor Pechtchanski
2003-05-05 16:40 ` Bug report Christopher Faylor
     [not found] <CAJVfQ_gj3N5+j+NpJytcYqMnMVMj-_p=EuLKsZ7BwnYWNRMgJg@mail.gmail.com>
2023-09-06 22:20 ` bug report Asad Ali
2023-09-08  5:09   ` Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2022-02-08 22:01 Bug Report julie77793
2022-02-09  6:29 ` Ernie Rael
2022-02-09 16:24 ` Bill Stewart
2001-06-06 22:21 Bug report David L Wiltshire
     [not found] <19980630141709.614.rocketmail@send101.yahoomail.com>
1998-07-01  8:02 ` Bug Report Ronald Pijnacker
     [not found] ` <199807010655.IAA00527.cygnus.gnu-win32@surgery1.best.ms.philips.com>
1998-07-02  9:53   ` Christopher G. Faylor
1997-02-17  8:27 bug report p.a.c.tavares
1997-02-16 22:10 Sean McNeil
1997-02-13  1:21 Sergey Okhapkin
1997-02-12 16:36 Andres Takach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.44.0305051236270.25128-100000@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    --cc=kern@sibbald.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).