ds
Oliver Old
Software Developer
LÖWEN ENTERTAINMENT GmbH
Saarlandstraße 240
55411 Bingen am Rhein
Germany
T: +49 6721 407319
Email: oliver@loewen.de
www.loewen.de / www.admiral-games.de
From: Jon Turney
Sent: Monday, October 16, 2023 5:11 PM
To: Old, Oliver ; The Cygwin Mailing List
Subject
On 11/10/2023 18:26, Old, Oliver via Cygwin wrote:
Good evening!
I have been looking for a way to debug programs on multiple targets of
different architectures via gdbserver. It seems that Cygwin currently doesn't
provide a gdb configured for this scenario.
The gdb from the Cygwin distributio
Hello all,
any news here eventually ?
Kind Regards
Ariel Burbaickij
On Mon, Jun 27, 2022 at 1:46 PM Ariel Burbaickij
wrote:
> OK, it crashes very close to the initial spot also in latest&greatest
> 12.1:
>
> 1048 void* __place = _Raw_bytes_alloc(__alloc).allocate(__size);
> (gdb) s
>
OK, it crashes very close to the initial spot also in latest&greatest
12.1:
1048 void* __place = _Raw_bytes_alloc(__alloc).allocate(__size);
(gdb) s
__gnu_cxx::new_allocator::allocate (__n=85, this=)
at
/usr/src/debug/gcc-11.3.0-1/x86_64-pc-cygwin/libstdc++-v3/include/ext/new_alloca
OK, thank you for your reply. Will do and will let you know.
Reproducibility, should details of it be needed, is not an issue as the
program I tried to debug is open-source and easily available.
Kind Regards
Ariel Burbaickij
On Sunday, June 26, 2022, Jon Turney wrote:
> On 24/06/2022 15:13, Ari
On 24/06/2022 15:13, Ariel Burbaickij wrote:
Hello mailing list,
I was in the middle of deep debugging session when following happened:
103 allocate(size_type __n, const void* = static_cast(0))
(gdb) s
__wrap__Znwm (sz=85) at
/usr/src/debug/cygwin-3.3.5-1/winsup/cygwin/libstdcxx_wrapp
On 07/05/2021 09:33, Takashi Yano via Cygwin wrote:
On Thu, 6 May 2021 21:31:27 +0100
Jon Turney wrote:
On 02/05/2021 17:16, Takashi Yano via Cygwin wrote:
On Sat, 6 Feb 2021 00:26:54 +0900
Takashi Yano wrote:
On Fri, 5 Feb 2021 19:34:57 +0900
Takashi Yano wrote:
On Tue, 26 Jan 2021 12:14:02
Hi Blaz,
Unfortunately, "it doesn't work" is not useful for diagnosing your
problem (https://www.chiark.greenend.org.uk/~sgtatham/bugs.html#respect).
What did you do? What happened? What did you expect to happen?
Csaba
On Wed, 29 Dec 2021 at 08:37, Blaz Stibelj wrote:
>
> Hello,
> I have an is
On 2021-11-19 08:08, Carter, Mark Andrew (Andy) via Cygwin wrote:
Gdb will not run an executable when it is a symbolic link in the post
Cygwin release 3.1.5 form. As seen below I am currently running
Cygwin 3.1.7. I have confirmed this is due to the change of the "ln
-s" implementation. Links c
On Thu, 6 May 2021 21:31:27 +0100
Jon Turney wrote:
> On 02/05/2021 17:16, Takashi Yano via Cygwin wrote:
> > On Sat, 6 Feb 2021 00:26:54 +0900
> > Takashi Yano wrote:
> >> On Fri, 5 Feb 2021 19:34:57 +0900
> >> Takashi Yano wrote:
> >>> On Tue, 26 Jan 2021 12:14:02 +0900
> >>> Takashi Yano wrote:
On 02/05/2021 17:16, Takashi Yano via Cygwin wrote:
On Sat, 6 Feb 2021 00:26:54 +0900
Takashi Yano wrote:
On Fri, 5 Feb 2021 19:34:57 +0900
Takashi Yano wrote:
On Tue, 26 Jan 2021 12:14:02 +0900
Takashi Yano wrote:
Hi GDB maintainer,
Sorry! I meant to go back and look at this, but I forgot.
On Sat, 6 Feb 2021 00:26:54 +0900
Takashi Yano wrote:
> On Fri, 5 Feb 2021 19:34:57 +0900
> Takashi Yano wrote:
> > On Tue, 26 Jan 2021 12:14:02 +0900
> > Takashi Yano wrote:
> > > Hi GDB maintainer,
> > >
> > > In GDB, debugged process cannot continue execution after break
> > > if it reads stdin
On Tue, Apr 27, 2021 at 3:14 PM Takashi Yano
wrote:
> On Tue, 27 Apr 2021 09:58:01 -0400
> "William M. \(Mike\) Miller via Cygwin" wrote:
> > I refreshed my Cygwin installation over the weekend, and ever since I
> have
> > not been able to run gdb under emacs as I previously had done. I use M-x
On Tue, 27 Apr 2021 09:58:01 -0400
"William M. \(Mike\) Miller via Cygwin" wrote:
> I refreshed my Cygwin installation over the weekend, and ever since I have
> not been able to run gdb under emacs as I previously had done. I use M-x
> gdb to start the gud interface, and as soon as I enter the "ru
On Fri, 5 Feb 2021 19:34:57 +0900
Takashi Yano wrote:
> On Tue, 26 Jan 2021 12:14:02 +0900
> Takashi Yano wrote:
> > Hi GDB maintainer,
> >
> > In GDB, debugged process cannot continue execution after break
> > if it reads stdin.
> >
> > With the following steps, cat is terminated with error.
> >
On Tue, 26 Jan 2021 12:14:02 +0900
Takashi Yano wrote:
> Hi GDB maintainer,
>
> In GDB, debugged process cannot continue execution after break
> if it reads stdin.
>
> With the following steps, cat is terminated with error.
>
> 1) Install coreutils-debuginfo package.
> 2) Run "gdb cat" in consol
On 03.02.2021 22:40, Marco Atzeri wrote:
On 22.01.2021 00:30, Ken Brown via Cygwin wrote:
On 1/21/2021 5:27 PM, Tord Andreasson via Cygwin wrote:
Hi,
I encounter the same issue too.
I can replicate the issue if I run gdb from CMD
while from Mintty or Cygwin.bat it works fine.
It seems late
On 22.01.2021 00:30, Ken Brown via Cygwin wrote:
On 1/21/2021 5:27 PM, Tord Andreasson via Cygwin wrote:
Hi,
I encounter the same issue too.
gdb starts however there is no gdb prompt, nothing is echoed and
nothing is
printed on the bash window except an empty blank line. From now you
operate
On 1/21/2021 5:27 PM, Tord Andreasson via Cygwin wrote:
Hi,
I encounter the same issue too.
gdb starts however there is no gdb prompt, nothing is echoed and nothing is
printed on the bash window except an empty blank line. From now you operate
blindfolded.
Debugging a simple application that p
On Thursday, January 21, 2021, 05:29:27 PM EST, Tord Andreasson via Cygwin
wrote:
> I tried "strace -o /tmp/gdb.strace /usr/bin/gdb --version" and indeed there
>are lines with 37 error messages in it. Since the trace file is large (2MB)
$ Err_6.4.5.exe 0xC034 says:
STATUS_OBJECT_NAME_N
Hi,
I encounter the same issue too.
gdb starts however there is no gdb prompt, nothing is echoed and nothing is
printed on the bash window except an empty blank line. From now you operate
blindfolded.
Debugging a simple application that prints "Hello World" on file
demonstrates that gdb loads th
On 21.01.2021 20:02, Daniel, Barry K. via Cygwin wrote:
I am trying to build and debug a linux application on a Windows 10 machine. I have installed Cygwin64 with GDB and the GCC compliers.
When I open up a Cygwin64 terminal and type "gcc -version" or "g++ --version" I get the normal informati
please reply to the mailing list
On 21.01.2021 15:39, Tord Andreasson wrote:
Hi Marco,
I did not think about that, and I really wonder if that is the root
cause behind the issue since the content of bash window remains the
same, without any blank lines (or lines using e.g. black text on a bla
On 21.01.2021 13:06, Tord Andreasson via Cygwin wrote:
Hi,
torda@Tord-desktop ~ /HelloWorld
$ gdb ./helloworld.exe
run
quit
torda@Tord-desktop ~/HelloWorld
$
Hopefully this description is comprehensible, if not please let me know if
anything is missing.
Any idea what I should look at to
On Monday, January 18, 2021 6:42 PM Ken Brown wrote:
>On 1/18/2021 12:35 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
>>> I was asking for the strace output. It might just show the same DLL loading
>>> issues that Marco noticed, or it might show som
On 1/18/2021 12:35 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
I was asking for the strace output. It might just show the same DLL loading
issues that Marco noticed, or it might show something more.
Ok, here are the first 100 lines, the whole th
On Monday, January 18, 2021 5:53 PM Ken Brown wrote:
>
>[Resending. Accidentally sent to OP instead of list.]
{Happens here too. Reply All or Reply (in Outlook) both send to OP instead of
list.]
>
>On 1/18/2021 8:08 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ke
[Resending. Accidentally sent to OP instead of list.]
On 1/18/2021 8:08 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
On 15/01/2021 12:28
On 1/18/2021 8:54 AM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, Januar
On Monday, January 18, 2021 2:54 PM Lemke, Michael SF/HZA-ZIC2 wrote:
>On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
>On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Monday, January 18, 2021 2:23 PM Marco Atzeri wrote:
>On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>>> On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
> On 15/
On 18.01.2021 14:08, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
On 15/01/2021 12:28, Lemke, Michael wrote:
I just installed a fresh copy of
On Friday, January 15, 2021 9:02 PM Ken Brown wrote:
>On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
>> On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>>> On 15/01/2021 12:28, Lemke, Michael wrote:
I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
Howe
On 1/15/2021 1:47 PM, Lemke, Michael SF/HZA-ZIC2 wrote:
On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
On 15/01/2021 12:28, Lemke, Michael wrote:
I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
However, gdb does not produce any output.
Installing gdb versions 7.9.
On Friday, January 15, 2021 4:45 PM Jon Turney wrote:
>On 15/01/2021 12:28, Lemke, Michael wrote:
>> I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
>> However, gdb does not produce any output.
>>
>> Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
On 15/01/2021 12:28, Lemke, Michael SF/HZA-ZIC2 wrote:
I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
However, gdb does not produce any output.
Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
Any ideas why?
[...]
Install gdb 7.12.1-2
pc> gd
On 15.01.2021 13:28, Lemke, Michael SF/HZA-ZIC2 wrote:
I just installed a fresh copy of Cygwin and gdb with setup-x86_64.exe.
However, gdb does not produce any output.
Installing gdb versions 7.9.1-1 and 7.10.1-1 work, anything newer doesn't.
Any ideas why?
Problem reports: https://cygw
I used cygwin64 terminal (C:\cygwin64\bin\mintty.exe) to generate these
files.
I tried gdb on both cygwin64 terminal and window command prompt.
I don't get any output on both of them
Il giorno ven 8 gen 2021 alle ore 14:04 Marco Atzeri
ha scritto:
> On 08.01.2021 12:46, Gaetano Buldo wrote:
> >
On 08.01.2021 12:46, Gaetano Buldo wrote:
Hi Marco,
i attach the files.
I a first moment I installed the last versions of all the tools, after
that i tried install other version.
That's why my current version of gcc is 9.3.0-2.
I removed some sensitive info, i putted .
Thanks,
Gaetano
On 08.01.2021 10:20, Gaetano Buldo via Cygwin wrote:
Hello,
I installed Cygwin for 64bit window, and the following tools in order to
build and debug c programs using eclipse.
gcc 9.3.0-2
why not the version 10 ?
make 4.3-1
gdb 9.2-1
It seems like the gdb program doesn't print on the terminal.
On Sat, Oct 31, 2020 at 02:09:28PM +0900, cygwin wrote:
> On Sat, 31 Oct 2020 14:56:14 +1100, Duncan Roe
> > On Sat, Oct 31, 2020 at 02:30:07PM +1100, Duncan Roe wrote:
> > > Hi,
> > >
> > > Updated cygwin64 this morning and now gdb won't start.
> > >
> > > cygcheck shows 2 missing libraries:
> > >
On Sat, 31 Oct 2020 14:56:14 +1100, Duncan Roe
> On Sat, Oct 31, 2020 at 02:30:07PM +1100, Duncan Roe wrote:
> > Hi,
> >
> > Updated cygwin64 this morning and now gdb won't start.
> >
> > cygcheck shows 2 missing libraries:
> >
> > 14:10:32$ cygcheck gdb
> > Found: C:\cygwin64\bin\gdb.exe
> > C:\cy
On Sat, Oct 31, 2020 at 02:30:07PM +1100, Duncan Roe wrote:
> Hi,
>
> Updated cygwin64 this morning and now gdb won't start.
>
> cygcheck shows 2 missing libraries:
>
> 14:10:32$ cygcheck gdb
> Found: C:\cygwin64\bin\gdb.exe
> C:\cygwin64\bin\gdb.exe
> C:\cygwin64\bin\cygwin1.dll
> C:\Windows
Jon Turney wrote:
On 30/06/2020 04:24, Mark Geisert wrote:
Ken Brown via Cygwin wrote:
On 6/28/2020 9:31 AM, Jon Turney wrote:
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create a
core file t
On 30/06/2020 04:24, Mark Geisert wrote:
Ken Brown via Cygwin wrote:
On 6/28/2020 9:31 AM, Jon Turney wrote:
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to
create a core file that I could examine
Ken Brown via Cygwin wrote:
On 6/28/2020 9:31 AM, Jon Turney wrote:
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create a
core file that I could examine with gdb, but I apparently ran into a gdb
On 6/28/2020 9:31 AM, Jon Turney wrote:
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create a
core file that I could examine with gdb, but I apparently ran into a gdb bug.
I tried both gdb 9.2-
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create
a core file that I could examine with gdb, but I apparently ran into a
gdb bug. I tried both gdb 9.2-1 and 8.3.1-1. Here are the results with
On 30/12/2019 17:40, Jon Turney wrote:
The following package has been updated in the Cygwin distribution:
* gdb-8.3.1-1
The GNU debugger allows you to debug programs written in C, C++, and
other languages, by executing them in a controlled fashion and printing
their data.
This is an update
Am 29.12.2019 um 13:58 schrieb Jon Turney:
On 28/12/2019 21:27, Marco Atzeri wrote:
Hi,
I am trying to debug the libuv test failures,
but it seems I am not able to convince GDB on stopping
just before the failure.
I think that the problem here is that the libuv test runner forks() to
run each
On 28/12/2019 21:27, Marco Atzeri wrote:
Hi,
I am trying to debug the libuv test failures,
but it seems I am not able to convince GDB on stopping
just before the failure.
I think that the problem here is that the libuv test runner forks() to
run each test in a subprocess.
I don't think 'set
Am 29.12.2019 um 05:38 schrieb Brian Inglis:
On 2019-12-28 15:28, Marco Atzeri wrote:
Am 28.12.2019 um 23:03 schrieb Ken Brown:
On 12/28/2019 4:27 PM, Marco Atzeri wrote:
I am trying to debug the libuv test failures,
but it seems I am not able to convince GDB on stopping
just before the failur
On 2019-12-28 15:28, Marco Atzeri wrote:
> Am 28.12.2019 um 23:03 schrieb Ken Brown:
>> On 12/28/2019 4:27 PM, Marco Atzeri wrote:
>>> I am trying to debug the libuv test failures,
>>> but it seems I am not able to convince GDB on stopping
>>> just before the failure.
>>>
>>> Is "thread apply all"
Am 28.12.2019 um 23:03 schrieb Ken Brown:
On 12/28/2019 4:27 PM, Marco Atzeri wrote:
Hi,
I am trying to debug the libuv test failures,
but it seems I am not able to convince GDB on stopping
just before the failure.
Is "thread apply all" working on Cygwin ?
The fact that produces no output in co
On 12/28/2019 4:27 PM, Marco Atzeri wrote:
> Hi,
> I am trying to debug the libuv test failures,
> but it seems I am not able to convince GDB on stopping
> just before the failure.
>
> Is "thread apply all" working on Cygwin ?
> The fact that produces no output in comparison to
> a normal break co
On 10/12/2017 1:24 PM, Jon Turney wrote:
On 11/10/2017 21:32, Ken Brown wrote:
On 10/11/2017 3:44 PM, Jon Turney wrote:
On 27/09/2016 21:15, Ken Brown wrote:
On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
Using program foo:
program foo
e = 1.0
stop
end
$ /usr/bin/gfo
On 11/10/2017 21:32, Ken Brown wrote:
On 10/11/2017 3:44 PM, Jon Turney wrote:
On 27/09/2016 21:15, Ken Brown wrote:
On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
Using program foo:
program foo
e = 1.0
stop
end
$ /usr/bin/gfortran -g foo.f -o foo
Emacs version in
On 10/11/2017 3:44 PM, Jon Turney wrote:
On 27/09/2016 21:15, Ken Brown wrote:
On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
Using program foo:
program foo
e = 1.0
stop
end
$ /usr/bin/gfortran -g foo.f -o foo
Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, G
On 27/09/2016 21:15, Ken Brown wrote:
On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
Using program foo:
program foo
e = 1.0
stop
end
$ /usr/bin/gfortran -g foo.f -o foo
Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version
3.18.9) of 2016-09-17
Insid
On 19/10/2016 17:46, Rockefeller, Harry wrote:
I can confirm that this happens also with gdb-7.11.1-1 but not
gdb-7.10.1-1. (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
It also fails with M-x gdb instead of M-x gud-gdb, but with a different error
message:
Failed to resume program
On 10/09/2016 12:39, Jon Turney wrote:
On 09/09/2016 05:15, Reto Huber wrote:
I am using cygwin for quite a while. Yesterday I did update.
Everything seemed to work smooth. Today I figured out that gdb does no
longer work debugging my project. Even a simple "Hello World" can not
be debugged anym
Sent: Wednesday, October 19, 2016 10:30 AM
>> >To: cygwin@cygwin.com
>> >Subject: Re: gdb 7.11.1-2 started within emacs fails
>> [snip]
>> >>>I can confirm that this happens also with gdb-7.11.1-1 but not
>> >>>gdb-7.10.1-1. (I tested on x86_64, si
On Oct 19 12:46, Rockefeller, Harry wrote:
> >-Original Message-
> >From: cygwin-ow...@cygwin.com [mailto:cygwin->ow...@cygwin.com] On Behalf Of
> >William M. (Mike) Miller
> >Sent: Wednesday, October 19, 2016 10:30 AM
> >To: cygwin@cygwin.com
> >S
>-Original Message-
>From: cygwin-ow...@cygwin.com [mailto:cygwin->ow...@cygwin.com] On Behalf Of
>William M. (Mike) Miller
>Sent: Wednesday, October 19, 2016 10:30 AM
>To: cygwin@cygwin.com
>Subject: Re: gdb 7.11.1-2 started within emacs fails
[snip]
>>>I
On Thu, Sep 29, 2016 at 11:21 AM, Rockefeller, Harry
wrote:
>
>>-Original Message-
>>From: cygwin-ow...@cygwin.com [mailto:cygwin->ow...@cygwin.com] On Behalf Of
>>Ken Brown
>>Sent: Tuesday, September 27, 2016 3:16 PM
>>To: cygwin@cygwin.com
>&g
>-Original Message-
>From: cygwin-ow...@cygwin.com [mailto:cygwin->ow...@cygwin.com] On Behalf Of
>Ken Brown
>Sent: Tuesday, September 27, 2016 3:16 PM
>To: cygwin@cygwin.com
>Subject: Re: gdb 7.11.1-2 started within emacs fails
>On 9/27/2016 2:47 PM, Rockefelle
On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
Using program foo:
program foo
e = 1.0
stop
end
$ /usr/bin/gfortran-g foo.f -o foo
Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 3.18.9) of
2016-09-17
Inside emacs I ran M-x gud-gdb and got
... GN
On 26/09/2016 14:41, Jon Turney wrote:
On 22/09/2016 20:55, Rockefeller, Harry wrote:
gdb (test version) and program's 'read' seem to have an input clash.
Anyway, gdb used to pause and allow keyboard input.
Thanks for reporting this problem, and the test case.
Thread 1 "foo" hit Breakpoint 1
On 22/09/2016 20:55, Rockefeller, Harry wrote:
gdb (test version) and program's 'read' seem to have an input clash.
Anyway, gdb used to pause and allow keyboard input.
Thanks for reporting this problem, and the test case.
Thread 1 "foo" hit Breakpoint 1, foo () at foo.f:4
4 write(
On 21/09/2016 22:06, Rockefeller, Harry wrote:
Program received signal ?, Unknown signal.
0x759cc54f in RaiseException ()
from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
(gdb)
This is the same problem as [1].
The workarounds mentioned there still apply.
[1] https://cygwin.com/ml/cygwin/2
On 21/09/2016 23:06, Rockefeller, Harry wrote:
With simple program, foo.f:
[begin literal]
program foo
implicit none
logical*4 e
e = .true.
stop
end
[end literal]
I get these results:
$ /usr/bin/gfortran-g foo.f -o foo
It runs fine for me.
Problem re
Hi Jon
Thanks a lot for your valuable help. I did update gdb to version
7.11.1-1 test release. Now it works fine.
Have a nice day,
Reto
On Sat, Sep 10, 2016 at 1:39 PM, Jon Turney wrote:
> On 09/09/2016 05:15, Reto Huber wrote:
>>
>> I am using cygwin for quite a while. Yesterday I did update.
On 09/09/2016 05:15, Reto Huber wrote:
I am using cygwin for quite a while. Yesterday I did update.
Everything seemed to work smooth. Today I figured out that gdb does no
longer work debugging my project. Even a simple "Hello World" can not
be debugged anymore. The executable itself runs ok. Here
On Jun 7 22:14, Takashi Yano wrote:
> On Mon, 6 Jun 2016 15:16:42 +0200 Corinna Vinschen wrote:
> > I uploaded a new snapshot with this patch to https://cygwin.com/snapshots/
> > for quick testing.
>
> I have tested the snapshot. It seems quite good. Thanks a lot.
>
> > Just one question: In fu
On Mon, 6 Jun 2016 15:16:42 +0200 Corinna Vinschen wrote:
> I uploaded a new snapshot with this patch to https://cygwin.com/snapshots/
> for quick testing.
I have tested the snapshot. It seems quite good. Thanks a lot.
> Just one question: In future, would you mind terribly to provide
> patches
On 6/6/2016 6:12 AM, Takashi Yano wrote:
Of course, Ken's gdbstc works fine without sleep with this patch,
as well as original emacs case.
Confirmed. Thanks.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: ht
On Jun 6 19:12, Takashi Yano wrote:
> Hi Corinna,
>
> I had looked into this problem, and found the cause.
>
> 'man termios' says:
> "A read(2) returns at most one line of input" in canonical mode.
>
> On cygwin 2.5.1, read(2) returns all data in buffer if the buffer
> size specified is large e
Hi Corinna,
I had looked into this problem, and found the cause.
'man termios' says:
"A read(2) returns at most one line of input" in canonical mode.
On cygwin 2.5.1, read(2) returns all data in buffer if the buffer
size specified is large enough. This behaviour is correct in
noncanonical mode,
> On Jun 1 16:01, Ken Brown wrote:
> > On 6/1/2016 3:54 PM, Corinna Vinschen wrote:
> > > On Jun 1 15:05, Ken Brown wrote:
> > > > On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
> > > > > On Jun 1 11:22, Ken Brown wrote:
> > > > > > And this also fixes the original problem in emacs that started th
On Jun 1 16:01, Ken Brown wrote:
> On 6/1/2016 3:54 PM, Corinna Vinschen wrote:
> > On Jun 1 15:05, Ken Brown wrote:
> > > On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
> > > > On Jun 1 11:22, Ken Brown wrote:
> > > > > And this also fixes the original problem in emacs that started the
> > > > >
On 6/1/2016 3:54 PM, Corinna Vinschen wrote:
On Jun 1 15:05, Ken Brown wrote:
On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
On Jun 1 11:22, Ken Brown wrote:
And this also fixes the original problem in emacs that started the thread:
https://www.cygwin.com/ml/cygwin/2016-05/msg00318.html
I
On Jun 1 15:05, Ken Brown wrote:
> On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
> > On Jun 1 11:22, Ken Brown wrote:
> > > And this also fixes the original problem in emacs that started the thread:
> > >
> > > https://www.cygwin.com/ml/cygwin/2016-05/msg00318.html
> >
> > I reverted commit 25
On 6/1/2016 2:28 PM, Corinna Vinschen wrote:
On Jun 1 11:22, Ken Brown wrote:
On 6/1/2016 10:33 AM, Ken Brown wrote:
On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 1 09:02, Ken Brown wrote:
On 6/1/2016 8:51 AM, Ken Brown wrote:
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
On Jun 1 11:22, Ken Brown wrote:
> On 6/1/2016 10:33 AM, Ken Brown wrote:
> > On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
> > > Hi Ken,
> > >
> > > On Jun 1 09:02, Ken Brown wrote:
> > > > On 6/1/2016 8:51 AM, Ken Brown wrote:
> > > > > On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
> > > > > >
On 6/1/2016 10:33 AM, Ken Brown wrote:
On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 1 09:02, Ken Brown wrote:
On 6/1/2016 8:51 AM, Ken Brown wrote:
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
Any chance you could bisect Cygwin to help finding the culprit?
The culprit is
On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
Hi Ken,
On Jun 1 09:02, Ken Brown wrote:
On 6/1/2016 8:51 AM, Ken Brown wrote:
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
Any chance you could bisect Cygwin to help finding the culprit?
The culprit is
commit 252a07b0ad3353abcd0fcd9b1b65ff97
On Jun 1 16:28, Corinna Vinschen wrote:
> Hi Ken,
>
> On Jun 1 09:02, Ken Brown wrote:
> > On 6/1/2016 8:51 AM, Ken Brown wrote:
> > > On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
> > > > Any chance you could bisect Cygwin to help finding the culprit?
> > >
> > > The culprit is
> > >
> > > co
Hi Ken,
On Jun 1 09:02, Ken Brown wrote:
> On 6/1/2016 8:51 AM, Ken Brown wrote:
> > On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
> > > Any chance you could bisect Cygwin to help finding the culprit?
> >
> > The culprit is
> >
> > commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
> > Author: Tak
Hi Takashi,
can you please have a look?
Thanks,
Corinna
On Jun 1 08:51, Ken Brown wrote:
> On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
> > Any chance you could bisect Cygwin to help finding the culprit?
>
> The culprit is
>
> commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
> Author: Taka
On 6/1/2016 8:51 AM, Ken Brown wrote:
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
Any chance you could bisect Cygwin to help finding the culprit?
The culprit is
commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
Author: Takashi Yano
Date: Fri Apr 3 13:07:35 2015 +0900
Cygwin hangs up if
On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
Any chance you could bisect Cygwin to help finding the culprit?
The culprit is
commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
Author: Takashi Yano
Date: Fri Apr 3 13:07:35 2015 +0900
Cygwin hangs up if several keys are typed during outputti
On May 30 18:41, Ken Brown wrote:
> On 5/30/2016 4:02 PM, Ken Brown wrote:
> > On 5/26/2016 8:31 AM, Ken Brown wrote:
> > > This looks like a bug I reported several years ago; it actually has
> > > nothing to do with emacs:
> > >
> > > https://www.cygwin.com/ml/cygwin/2011-10/msg00445.html
> > >
On 5/30/2016 4:02 PM, Ken Brown wrote:
On 5/26/2016 8:31 AM, Ken Brown wrote:
This looks like a bug I reported several years ago; it actually has
nothing to do with emacs:
https://www.cygwin.com/ml/cygwin/2011-10/msg00445.html
It was fixed but then reappeared some months later:
https://ww
On Apr 12 21:16, Yaakov Selkowitz wrote:
> On 2016-04-12 10:20, Marco Atzeri wrote:
> >On 22/02/2016 10:00, Yaakov Selkowitz wrote:
> >>The following packages have been uploaded to the Cygwin distribution:
> >>
> >>* mesa-11.0.9-2
> >>* dri-drivers-11.0.9-2
> >>* libglapi0-11.0.9-2
> >>* libGL1-11.
On 21/01/2016 09:10, Tim Chick wrote:
Jon TURNEY wrote
On 14/01/2016 16:02, Tim Chick wrote:
Jon TURNEY wrote
I built a 32-bit version as well, but there was a slight delay with that
getting moved into the release. It should be mirroring out now, though.
Hi Jon,
I've just tried the 7.10.1
Jon TURNEY wrote
> On 14/01/2016 16:02, Tim Chick wrote:
>> Jon TURNEY wrote
>
> I built a 32-bit version as well, but there was a slight delay with that
> getting moved into the release. It should be mirroring out now, though.
Hi Jon,
I've just tried the 7.10.1-1 package, and it works fine fo
On 14/01/2016 16:02, Tim Chick wrote:
Jon TURNEY wrote
Can you provide some more information about what path realpath() is
failing for, and do you have any idea why?
The first one which fails for me is "c:\windows\system32\dgapi.dll"
I believe this is some security software installed on my ma
Jon TURNEY wrote
> Can you provide some more information about what path realpath() is
> failing for, and do you have any idea why?
The first one which fails for me is "c:\windows\system32\dgapi.dll"
I believe this is some security software installed on my machine by my
employer. I guess the sof
On 23/11/2015 15:09, Tim Chick wrote:
Am 08.10.2014 um 14:12 schrieb Corinna Vinschen:
On Sep 29 14:13, Dominik Straßer wrote:
Hi all,
Hi Corinna,
I've dug into the gdb sources. The problem is in the cygwin-only
part and is not about the PATH variable but about one single DLL
file name.
Thi
On Jan 12 13:34, Vanda Vodkamilkevich wrote:
> Hi,
>
> I'm reacting to this email with a long delay but I just wanted to let you
> know that this change saved my life, now I am finally able to debug again
> with cygwin (w7 64bits , 32 bits cygwin) because I was blocked by a nasty
> "security" dll
1 - 100 of 392 matches
Mail list logo
