> On Thu, Dec 15, 2005 at 02:45:59PM -0600, Van Sickle, Gary wrote:
> >In both cases tar *is* executed and works fine. Due to the Van
Sickle
> >Exclusion Principle (a bug and a debugging tool capable of providing
> >insight into that bug cannot occupy the same hardware at the same
> >time), not ru
On Thu, Dec 15, 2005 at 02:45:59PM -0600, Van Sickle, Gary wrote:
>In both cases tar *is* executed and works fine. Due to the Van Sickle
>Exclusion Principle (a bug and a debugging tool capable of providing
>insight into that bug cannot occupy the same hardware at the same
>time), not running unde
On Dec 14 20:07, Van Sickle, Gary wrote:
> > From: Corinna Vinschen
> > On Dec 14 15:00, Van Sickle, Gary wrote:
> > > OK, lessee what I missed:
> >
> > The error message content. When fixup_mmaps_after_fork fails, there's
> > a message in your window which gives at least some details for a
> st
>
> Could you do a:
>
> strace -ostrace.out bash
> tar --help
> exit
>
> and send the strace.out here as an attachment?
>
> cgf
I'll give it a try tomorrow.
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.c
On Wed, Dec 14, 2005 at 08:07:58PM -0600, Van Sickle, Gary wrote:
>> From: Corinna Vinschen
>> On Dec 14 15:00, Van Sickle, Gary wrote:
>> > OK, lessee what I missed:
>>
>> The error message content. When fixup_mmaps_after_fork fails, there's
>> a message in your window which gives at least some
> From: Christopher Faylor
> Were you just seeing the "fixup_mmaps_after_fork" error and nothing
> else? From the source, It looks like there should have been more
output
> than just that. If there wasn't anything other than that then I guess
> that's a clue.
>
Pretty much just that:
"
$ tar -
> From: Corinna Vinschen
> On Dec 14 15:00, Van Sickle, Gary wrote:
> > OK, lessee what I missed:
>
> The error message content. When fixup_mmaps_after_fork fails, there's
> a message in your window which gives at least some details for a
start.
>
"
$ tar --help
C:\cygwin\bin\bash.exe (3360):
On Dec 14 15:00, Van Sickle, Gary wrote:
> OK, lessee what I missed:
The error message content. When fixup_mmaps_after_fork fails, there's
a message in your window which gives at least some details for a start.
And why didn't you try strace? This would give a lot more details which
might help t
On Wed, Dec 14, 2005 at 03:00:14PM -0600, Van Sickle, Gary wrote:
>If not Corinna, please tell me what details I neglected to include via
>my report and/or my attached cygcheck -srv. Also helpful would be an
>answer to my question as to if a cygcheck from a 12-7 or -13 snapshot
>would be any more
lems.html.
>
>
> Corinna
OK, lessee what I missed:
"- Use a subject line that describes the issue well
Good examples:
"1.5.8: select bug (NT and 95)" [...]"
Guess we can add "recreate_mmaps_after_fork_failed errors post-11-30
snapshot" to that list.
"
On Dec 14 12:41, Van Sickle, Gary wrote:
> I'm getting a "recreate_mmaps_after_fork_failed" error on the 12-07 and
> 12-13 snapshots on one particular machine at work. That's pretty much
> all I get - rxvt dies immediately, and while I do get a bash prompt by
> using cmd.exe as my... ahem... "term
I'm getting a "recreate_mmaps_after_fork_failed" error on the 12-07 and
12-13 snapshots on one particular machine at work. That's pretty much
all I get - rxvt dies immediately, and while I do get a bash prompt by
using cmd.exe as my... ahem... "terminal"..., I can't run any programs
from it, not e
12 matches
Mail list logo
