From: "Łukasz Michalski" <l.michalski@ant.gliwice.pl>
To: <gdb@sources.redhat.com>
Subject: gdb crash
Date: Tue, 06 May 2003 19:58:00 -0000 [thread overview]
Message-ID: <HKEOLHPHNEIHIEKAOBLHAEIECNAA.l.michalski@ant.gliwice.pl> (raw)
Hi,
I am developing application using wxWindows for Linux and MS Windows
platforms using wxWindows. Under windows I am using mingw with latest
patches and Dev-Cpp (latest beta)
I have problems using gdb under windows. When I run my application
standalone everything works correct. But when run under gdb app crashes and
gdb crashes just after.
When I try to run app step-by-step by setting breakpoint to first line and
stepping over gdb crashes when accessing first static variable.
It crashes always with the same message:
Access violation in gdb exe. Memory at address 0x0000004 cannot be "read".
I want to generate reasonable bug report, but I have no idea how to do it.
My app with debug info has 45Mb and is linked with wxWindows compiled
with -g flag and some other smaller libraries also compiled with -g flag.
Here are versions of compiler and gdb:
C:\>gdb -v
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
[...]
This GDB was configured as "mingw32".
C:\>gcc -v
Reading specs from P:/DevCpp/bin/../lib/gcc-lib/mingw32/3.2/specs
Configured with:
../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as --host=
mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls --en
able
-languages=f77,c++,objc,ada --disable-win32-registry --disable-shared
Thread model: win32
gcc version 3.2 (mingw special 20020817-1)
I can try to strip the code, but cannot make my app independent of wxWindows
and I use slightly modified version than original.
I will be very graceful for any suggestions what to do to make gdb work.
Under Linux everything works fine.
Regards,
ÂŁukasz Michalski
next reply other threads:[~2003-05-06 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 19:58 Łukasz Michalski [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-10 18:44 Mathew Yeates
2010-08-10 19:26 ` Tom Tromey
2010-08-10 19:32 ` Mathew Yeates
2000-07-27 11:42 Tom Tromey
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=HKEOLHPHNEIHIEKAOBLHAEIECNAA.l.michalski@ant.gliwice.pl \
--to=l.michalski@ant.gliwice.pl \
--cc=gdb@sources.redhat.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).