public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "velteyn at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug win32/15716] Continuos false SEGMENTATION FAULTS debugging win32 application
Date: Wed, 10 Jul 2013 13:54:00 -0000	[thread overview]
Message-ID: <bug-15716-4717-cIkJqwdlvh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15716-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15716

--- Comment #8 from Edoardo <velteyn at gmail dot com> ---
OK I have many many evidences of my theory . I past 5 days to try and try GDB.

I cannot even attach to the task !!!

Into this thread you can find my experience and many files attach on that forum
 with evidences that GDB have many problems on windows !!!

Also my last compile with another gcc not changed the result !!

here is my forum posts on spring devel website 

http://springrts.com/phpbb/viewtopic.php?f=12&t=30677

many screen-shots there

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-07-10 13:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  7:45 [Bug win32/15716] New: " velteyn at gmail dot com
2013-07-03  7:48 ` [Bug win32/15716] " velteyn at gmail dot com
2013-07-03 10:45 ` palves at redhat dot com
2013-07-03 11:28 ` velteyn at gmail dot com
2013-07-03 11:37 ` palves at redhat dot com
2013-07-03 12:16 ` velteyn at gmail dot com
2013-07-04  9:55 ` velteyn at gmail dot com
2013-07-04  9:59 ` palves at redhat dot com
2013-07-10 13:54 ` velteyn at gmail dot com [this message]
2013-07-24 16:11 ` palves at redhat dot com
2013-07-25  7:13 ` velteyn at gmail dot com
2013-07-25 11:03 ` palves at redhat dot com
2021-10-29  7:43 ` loonyivy at gmail dot com
2021-10-29  8:21 ` velteyn at gmail dot com
2023-02-11 17:52 ` tromey at sourceware dot org

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=bug-15716-4717-cIkJqwdlvh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).