On 21/02/2023 19:04, Jon Turney via Cygwin wrote:
The following package has been updated in the Cygwin distribution:
* gdb-13.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
Good evening!
The difference in size is indeed a whopping 19M (8M -> 27M). That might be why
the Msys devs chose to split their gdb into a main package and a multi-arch
package that depends on the main package.
In case you decide to build gdb with 'enable-targets=all', de
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 C
On 03/10/2023 17:55, Johannes Thoma via Cygwin wrote:
Hi,
Am 03.10.23 um 17:03 schrieb Cedric Blancher via Cygwin:
On Tue, 26 Sept 2023 at 06:39, Cedric Blancher
wrote:
Good morning!
Is it possible to load Visual Studio (VC19, VC22) debug info (*.pdb
files) into Cygwin gdb?
Anyone?
Or
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 distribution isn't configured with
'--enable-ta
Hi,
Am 03.10.23 um 17:03 schrieb Cedric Blancher via Cygwin:
On Tue, 26 Sept 2023 at 06:39, Cedric Blancher
wrote:
Good morning!
Is it possible to load Visual Studio (VC19, VC22) debug info (*.pdb
files) into Cygwin gdb?
Anyone?
Or can VC19/VC22 create DWARF debug data?
Ced
As far as
On Tue, 26 Sept 2023 at 06:39, Cedric Blancher
wrote:
>
> Good morning!
>
> Is it possible to load Visual Studio (VC19, VC22) debug info (*.pdb
> files) into Cygwin gdb?
Anyone?
Or can VC19/VC22 create DWARF debug data?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/
Good morning!
Is it possible to load Visual Studio (VC19, VC22) debug info (*.pdb
files) into Cygwin gdb?
Ced
--
Cedric Blancher
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com
Greetings, Holger Machens!
> when starting gdb (v10 or higher) with a windows absolute path to an
> executable, it runs into issues with paths in several cases, reporting the
> following error:
> BFD: reopening /cygdrive/x/project/bin/X:\project\bin\simple.test.exe: No
> such fi
Hello there,
when starting gdb (v10 or higher) with a windows absolute path to an
executable, it runs into issues with paths in several cases, reporting
the following error:
BFD: reopening /cygdrive/x/project/bin/X:\project\bin\simple.test.exe:
No such file or directory
It looks like it
On 19/05/2022 17:05, Jon Turney wrote:
The following package has been updated in the Cygwin distribution:
* gdb-12.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
The following package has been updated in the Cygwin distribution:
* gdb-13.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 to the latest upstream version:
https
>Can you share a link to the gdb bug report?
https://sourceware.org/bugzilla/show_bug.cgi?id=29513
So, open source products' support reaction time is usually great but not
always great ;-). Unassigned for two months+ and counting.
Kind Regards
Ariel Burbaickij
On Wed, Nov 2, 2022 at
h the OCaml runtime.
[...]>>>
/cygdrive/d/a/scallywag/gdb/gdb-11.2-1.x86_64/src/gdb-11.2/gdb/infrun.c:2550
: internal-error: void resume_1(gdb_signal): Assertion
`pc_in_thread_step_range (pc, tp)' failed.
I'm not sure now which combination of stepping directly into the
malloc
On 19/10/2022 07:20, Ariel Burbaickij wrote:
Hello all,
I reported it already, of course as it happened to me but alas no reaction
so far.
Thanks for doing that.
Can you share a link to the gdb bug report?
--
Problem reports: https://cygwin.com/problems.html
FAQ
Hello David,
congrats on your bug fixing but gdb is pretty open that it considers it as
its own bug while running its "inferior", somewhere here:
if (tp->control.may_range_step)
{
/* If we're resuming a thread with the PC out of the step
range, then we're doing some n
OCaml runtime.
> >
> > At the moment, I know that we crash in malloc, so my main question is how to
> > go further in gdb. I installed the cygwin-debuginfo package, but all I'm
> > getting is:
>
> Firstly, if the crash is inside the cygwin DLL, you must follow the
&g
or debugging what
>> seems to be an unexpected interaction between mmap/mprotect/munmap and
>> malloc with the OCaml runtime.
>>
>> At the moment, I know that we crash in malloc, so my main question is how
>> to
>> go further in gdb. I installed the cygwin-debugin
to
go further in gdb. I installed the cygwin-debuginfo package, but all I'm
getting is:
Firstly, if the crash is inside the cygwin DLL, you must follow the
advice in [1], and use 'set cygwin-exceptions on' to tell gdb to stop on
an exception inside cygwin itself.
[1] https:/
I'm wondering if I may be able to have some pointers for debugging what
seems to be an unexpected interaction between mmap/mprotect/munmap and
malloc with the OCaml runtime.
At the moment, I know that we crash in malloc, so my main question is how to
go further in gdb. I installed the c
3.3 was coming out with a lot of new issues (as people were reporting),
so I just froze all upgrades. Looks like 3.3 is now stabilized as 3.4 is
getting ready LOL
> This was fixed in gdb-10.1-1 [1] (upstream in gdb 11) and cygwin 3.1.7.
Well, I've got cygwin 3.2.0 (which supposedly was exp
On 09/07/2022 01:58, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
The latest version of gdb that is not a test version is 11.2. But
you are using 9.2.
I am using the older dumper as well, my working cygwin is not cutting edge.
$ dumper -V
dumper (cygwin) 3.2.0
What I am coming at
On 2022-07-08 19:31, Backwoods BC wrote:
On Fri, Jul 8, 2022 at 5:59 PM Lavrentiev, Anton (NIH/NLM/NCBI) wrote:
The latest version of gdb that is not a test version is 11.2. But
you are using 9.2.
I am using the older dumper as well, my working cygwin is not cutting edge.
$ dumper -V
dumper
On Fri, Jul 8, 2022 at 5:59 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin wrote:
>
> > The latest version of gdb that is not a test version is 11.2. But
> > you are using 9.2.
>
> I am using the older dumper as well, my working cygwin is not cutting edge.
>
> $
> The latest version of gdb that is not a test version is 11.2. But
> you are using 9.2.
I am using the older dumper as well, my working cygwin is not cutting edge.
$ dumper -V
dumper (cygwin) 3.2.0
What I am coming at is that if dumper is not consistent with gdb,
that does not make any
On Fri, 8 Jul 2022 23:09:27 +
"Lavrentiev, Anton \(NIH/NLM/NCBI\) \[C\] wrote:
> > Try using a more recent gdb. I just tried your test case with gdb-12.1-1
> > (available as a test release), and it seemed to work.
>
> Thanks for the quick response... Though I'd
> Try using a more recent gdb. I just tried your test case with gdb-12.1-1
> (available as a test release), and it seemed to work.
Thanks for the quick response... Though I'd rather not use test releases.
The dumper binary and gdb in my case are supposed to be consistent with
-xr-x 1 ANTON None 161487 Jul 8 17:41 a.exe*
-rw-r--r-- 1 ANTON None 3331640 Jul 8 17:46 a.exe.core
$ file a.*
a.c:C source, ASCII text
a.exe: PE32+ executable (console) x86-64, for MS Windows
a.exe.core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV)
BUT: gdb does not want this
Jul 8 17:46 a.exe.core
$ file a.*
a.c:C source, ASCII text
a.exe: PE32+ executable (console) x86-64, for MS Windows
a.exe.core: ELF 64-bit LSB core file, x86-64, version 1 (SYSV)
BUT: gdb does not want this core file:
$ gdb ./a.exe a.exe.core
GNU gdb (GDB) (Cygwin 9.2-1) 9.2
Copyright
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(__
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
: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> void*>(0))
>> (gdb) s
>> __wrap__Znwm (sz
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
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_wrapper.cc:55
55return (*user_data
On 19/05/2022 13:19, abel.asmel...@att.net wrote:
Hello Jon,
I am running the Setup.X86_64.exe program and selecting packages from the
screen below and I don't see GDB package. Please, tell me what I am doing
wrong.
You need to change the 'View' selected at the top left f
The following package has been updated in the Cygwin distribution:
* gdb-12.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 to the latest upstream version:
https
On 5/19/2022 7:00 AM, abel.asmel...@att.net wrote:
Hello Cygwin Contributors,
I am trying to install GDB in Cygwin using the Setup_X86_64.exe Cygwin
installation program. However, I don't see the option of GDB source in the
package installation selection panel. What package should I u
On 19/05/2022 12:00, abel.asmel...@att.net wrote:
Hello Cygwin Contributors,
I am trying to install GDB in Cygwin using the Setup_X86_64.exe Cygwin
installation program. However, I don't see the option of GDB source in the
package installation selection panel. What package should I u
Hello Cygwin Contributors,
I am trying to install GDB in Cygwin using the Setup_X86_64.exe Cygwin
installation program. However, I don't see the option of GDB source in the
package installation selection panel. What package should I use to install
GDB debugger? Please, help.
Re
I am unable to find the package source that installs GDB in the
setup_x86_64.exe. Which package should I select to install the GDB debugger?
I only see gd-debuginfo package in the source list. Please, help.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https
handling.
Even with the following setting (by default),
(gdb) info signal SIGINT
SignalStop Print Pass to program Description
SIGINTYes Yes No Interrupt
inferior receives SIGINT when Ctrl-C is pressed.
Due to this behaviour, inferior cannot be continued
wever, I noticed another problem in signal handling.
> > > >
> > > > Even with the following setting (by default),
> > > > (gdb) info signal SIGINT
> > > > SignalStop Print Pass to program Description
> > > > SIGINT
On Tue, 25 Jan 2022 00:01:53 +0900
Takashi Yano wrote:
> On Mon, 24 Jan 2022 14:46:20 +
> Jon Turney wrote:
> > On 19/01/2022 09:39, Takashi Yano wrote:
> > >
> > > However, I noticed another problem in signal handling.
> > >
> > > Even wit
On Mon, 24 Jan 2022 14:46:20 +
Jon Turney wrote:
> On 19/01/2022 09:39, Takashi Yano wrote:
> >
> > However, I noticed another problem in signal handling.
> >
> > Even with the following setting (by default),
> > (gdb) info signal SIGINT
> > Signal
On 19/01/2022 09:39, Takashi Yano wrote:
However, I noticed another problem in signal handling.
Even with the following setting (by default),
(gdb) info signal SIGINT
SignalStop Print Pass to program Description
SIGINTYes Yes No Interrupt
inferior
coreutils-debuginfo package.
> 2) Run "gdb cat" in console (command prompt), not in mintty.
> 3) Enter "start" in gdb.
> 4) Enter "cont" in gdb.
>
> This results in:
> /usr/bin/cat: -: Input/output error
Thanks.
However, I noticed another problem in sign
The following package has been updated in the Cygwin distribution:
* gdb-11.2-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 to the latest upstream version:
https
+0900
Takashi Yano wrote:
Hi GDB maintainer,
Sorry! I meant to go back and look at this, but I forgot.
Thanks for reminding me!
Thanks for replying.
I've included this patch in the gdb-11.22-1 test package.
I don't think this patch is upstreamable as is.
I guess I'd like
t; Hello,
> I have an issue that last version of gdb file (Cygwin GNU Debugger) is not
> working with version of NetBeans 12.6 IDE on Win10.
> When I install older version of gdb file, the system work fine.
> Can you please check the situation.
>
> Thank you,
> Blaz
>
&g
Hello,
I have an issue that last version of gdb file (Cygwin GNU Debugger) is not
working with version of NetBeans 12.6 IDE on Win10.
When I install older version of gdb file, the system work fine.
Can you please check the situation.
Thank you,
Blaz
--
Problem reports: https://cygwin.com
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" implementat
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
created by Cygwin 2.8 and 3.1.0 work with this gdb ve
lse
>char *strsignal (int __signo); /* see
>/usr/include/string.h on cygwin */
>#endif
> o then it compiles, however a library is missed now:
> + x86_64-pc-cygwin/bin/ld:
> event-top.o:.../insight/bundle/gdb/event-top.c:8
Hello,
when compiling binutils-gdb I got stuck with an error concerning the strsignal
function.
This also occurs when trying to compile the insight gdb-frontend on cygwin64
that I tried to build.
* platform:
o cygwin 64bit on Win-10
o gcc (GCC) 11.2.0, g++ (GCC) 11.2.0
* commands
On 02/05/2021 15:54, Jon Turney wrote:
The following package has been updated in the Cygwin distribution:
* gdb-10.2-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
Greetings, Jim Hyslop!
> I've installed the php-debuginfo extension for gdb, but I can't figure
> out how to set a breakpoint with it. Is there a manual for
> php-debuginfo? All I can find is the package information.
> I'm trying to debug why a unit test is pa
As much as I love GDB dearly and rely on it regularly you might want
to have a look at netbeans.apache.org which is also free and a more
general fancy UI IDE. If it's a web site you're developing for example
it will let you fire up a browser, put breakpoints in the php code,
a
There's the "Magic Method" in PHP for __debuginfo()
<https://www.php.net/manual/en/language.oop5.magic.php#object.debuginfo>.
Also see PHP RFC: __debugInfo() <https://wiki.php.net/rfc/debug-info>.
You may have better luck asking the PHP devs how to best use this with G
Hi, all
I've installed the php-debuginfo extension for gdb, but I can't figure
out how to set a breakpoint with it. Is there a manual for
php-debuginfo? All I can find is the package information.
I'm trying to debug why a unit test is passing (it should fail). I'
2021 12:14:02 +0900
> >>> Takashi Yano wrote:
> >>>> Hi GDB maintainer,
>
> Sorry! I meant to go back and look at this, but I forgot.
>
> Thanks for reminding me!
Thanks for replying.
> >>>> In GDB, debugged process cannot continue execut
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 con
The following package has been updated in the Cygwin distribution:
* gdb-10.2-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 to the latest upstream version:
https
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
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
On 08.02.2021 16:33, matthew patton wrote:
On Sun, Feb 7, 2021 at 4:13 PM Jon Turney wrote:
>> It seems that gdb wants to run 'iconv -l' to list the available
encodings.
>>
>> It looks like perhaps an upstream bug that gdb outputs nothing when
>> iconv
On Sun, Feb 7, 2021 at 4:13 PM Jon Turney wrote:
>> It seems that gdb wants to run 'iconv -l' to list the available encodings.
>>
>> It looks like perhaps an upstream bug that gdb outputs nothing when
>> iconv can't be found (rather than using the defa
On Sun, Feb 7, 2021 at 4:13 PM Jon Turney wrote:
>
>
> It seems that gdb wants to run 'iconv -l' to list the available encodings.
>
> It looks like perhaps an upstream bug that gdb outputs nothing when
> iconv can't be found (rather than using the default
.
It seems that the GDB package should set a dependency on libiconv.
I had libiconv2 installed. Is that somehow related?
gdb always needed the shared lib in libiconv2
$ cygcheck /usr/bin/gdb.exe | grep iconv
D:\cygwin64\bin\cygiconv-2.dll
$ cygcheck -f /usr/bin/cygiconv-2.dll
libiconv2
into this problem and found this issue causes if iconv
cannot be found in the search path.
Installing libiconv package should solve the issue, I guess.
I can confirm that installing libiconv solves the problem. So it
was not a case of BLODA here.
It seems that the GDB package should set a
more of them
Maybe Takashi or Jon can provide hints on the matter.
I looked into this problem and found this issue causes if iconv
cannot be found in the search path.
Installing libiconv package should solve the issue, I guess.
It seems that the GDB package should set a dependency on libiconv
Hi Marco,
>> > it seems stacked and when blindly typing "quit" it responds with exiting.
>> > So it seems like the output is invisible.
>> > Tested it with Win7_32bit, GDB version 9.2-1 with Cygwin/bin in PATH
>> > (since the beginning).
>> >
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 fol
nds with exiting.
> > So it seems like the output is invisible.
> > Tested it with Win7_32bit, GDB version 9.2-1 with Cygwin/bin in PATH (since
> > the beginning).
> >
> > Regards
> > Daniel
>
> I can not fully replicate on my W10,
>
> bu
;> Hi Marco,
>>> it seems stacked and when blindly typing "quit" it responds with exiting.
>>> So it seems like the output is invisible.
>>> Tested it with Win7_32bit, GDB version 9.2-1 with Cygwin/bin in PATH (since
>>> the beginning).
>>&
onds with exiting. So
>> it seems like the output is invisible.
>> Tested it with Win7_32bit, GDB version 9.2-1 with Cygwin/bin in PATH (since
>> the beginning).
>>
>> Regards
>> Daniel
>
>I can not fully replicate on my W10,
>
>but I notice that runn
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 packag
On 05.02.2021 08:55, Daniel Röhrborn via Cygwin wrote:
On 04.02.2021 13:13, Daniel Röhrborn via Cygwin wrote:
Hi Marco,
it seems stacked and when blindly typing "quit" it responds with exiting. So it
seems like the output is invisible.
Tested it with Win7_32bit, GDB version
>On 04.02.2021 13:13, Daniel Röhrborn via Cygwin wrote:
>> I have this issue on three different PCs (Win7_32bit, 2x Win10_64bit) with
>> the latest Cygwin installer.
>> I installed Cygwin gcc/g++/gdb. Compiler works but gdb doesn't output
>> anything when started
On 04.02.2021 13:13, Daniel Röhrborn via Cygwin wrote:
I have this issue on three different PCs (Win7_32bit, 2x Win10_64bit) with the
latest Cygwin installer.
I installed Cygwin gcc/g++/gdb. Compiler works but gdb doesn't output anything
when started. It seems to have blocked right after
On Thursday, February 4, 2021 1:13 PM Daniel Röhrborn wrote:
>I have this issue on three different PCs (Win7_32bit, 2x Win10_64bit) with the
>latest Cygwin installer.
>I installed Cygwin gcc/g++/gdb. Compiler works but gdb doesn't output anything
>when started. It seems to h
I have this issue on three different PCs (Win7_32bit, 2x Win10_64bit) with the
latest Cygwin installer.
I installed Cygwin gcc/g++/gdb. Compiler works but gdb doesn't output anything
when started. It seems to have blocked right after start. What could cause this
behaviour?
When I downgra
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
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
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 console (command prompt), not in mintty.
3) Enter "start&qu
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
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
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
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&qu
black
background) added as I type commands, except from when I type quit, then
the window returns to the bash prompt.
Let me try to describe the behavior I experience. The last 3 lines in
the bash windows are as follows:
torda@Tord-desktop/
$ gdb
new blank line. Whatever command I type in gdb
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
Hi,
I just updated my cygwin 64 bit installation in order to resume a
programming project that I left aside quite some time ago.
Everything seems to work as it used to as I am able to pick up the project
where I left it, I can build and run the application however gdb I/O seems
broken.
Here are
emCore\mfehcthe.dll at 52b5
>> --- Process 32204 loaded C:\Program Files\McAfee\Endpoint Security\Adaptive
>> Threat Protection\mfedeeprem64.dll at 7fffcc70
>
>This could be the culprit. Can you exclude your Cygwin directory from McAfee?
Unfortunately not. It is man
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
y 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 Cy
: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.
Any ideas why?
[...]
Install gdb 7.12.1-2
pc> gdb -v
Install gdb
, 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.
Also ldd `which gdb` is
fine.
Please show the output.
pc> ldd `which
ael 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, gd
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.
>>>>>>
>&g
of Cygwin and gdb with setup-x86_64.exe.
However, gdb does not produce any output.
Also ldd `which gdb` is
fine.
Please show the output.
pc> ldd `which gdb`
cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3fdf6)
cygstdc++-6.dll => /usr/bin/cygstd
1 - 100 of 1150 matches
Mail list logo
