public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "info at michaelzeilfelder dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/13711] New: Stepping problem with different -fno-exception settings in library and application in 32-bit
Date: Mon, 20 Feb 2012 01:24:00 -0000	[thread overview]
Message-ID: <bug-13711-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13711
           Summary: Stepping problem with different -fno-exception
                    settings in library and application in 32-bit
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: info@michaelzeilfelder.de
    Classification: Unclassified


Created attachment 6228
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6228
Sources for a lib + application + Makefiles to reproduce the problem

I can't step into certain functions when a (static) library and an application
have used different settings for the -fno-exceptions flag in gcc. 

A C++ example is attached. It's reduced to the minimal code I was able to find
which still reproduced the problem.

I tested several gdb versions and interestingly I could only ever reproduce it
on a 32-bit system, while the same example works on a 64-bit system.

Reproduced with:
"GNU gdb (GDB) 7.4.50.20120206-cvs"
and with "GNU gdb (GDB) 7.0.1-debian" - both times on a 32-bit Debian "squeeze"
system.

_NOT_ reproduced (aka it worked correct) on:
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 on a 64-bit Ubuntu system.

To reproduce it decompress fnoexception.tar.gz (on a 32-bit system) and call:
> cd lib
> make
> cd ..
> make
> gdb mybug
> b main.cpp:10
> r
> s 

You can press s a few times and the expected behavior would be that it steps
into reader1->read().

Alternatively use the batchfile:
> ./reproduceit.sh 
> s

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


                 reply	other threads:[~2012-02-20  1:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-13711-4717@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).