From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-5751-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 14545 invoked by alias); 21 Nov 2007 14:58:01 -0000
Received: (qmail 14529 invoked by uid 71); 21 Nov 2007 14:58:01 -0000
Resent-Date: 21 Nov 2007 14:58:01 -0000
Resent-Message-ID: <20071121145801.14528.qmail@sourceware.org>
Resent-From: gdb-gnats@sources.redhat.com (GNATS Filer)
Resent-To: nobody@sources.redhat.com
Resent-Cc: gdb-prs@sources.redhat.com
Resent-Reply-To: gdb-gnats@sources.redhat.com, fabian.lenzen@web.de
Received: (qmail 13172 invoked by uid 48); 21 Nov 2007 14:50:41 -0000
Message-Id: <20071121145041.13171.qmail@sourceware.org>
Date: Wed, 21 Nov 2007 14:58:00 -0000
From: fabian.lenzen@web.de
Reply-To: fabian.lenzen@web.de
To: gdb-gnats@sources.redhat.com
X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31)
Subject: win32/2365: breaks by line number in dll are not triggered
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2007-q4/txt/msg00118.txt.bz2


>Number:         2365
>Category:       win32
>Synopsis:       breaks by line number in dll are not triggered
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 21 14:58:01 UTC 2007
>Closed-Date:
>Last-Modified:
>Originator:     fabian.lenzen@web.de
>Release:        MinGW 5.2.1
>Organization:
>Environment:
Windows XP32
MinGW GNU compiler 3.4.2
>Description:
(working in C++)
Breakpoints set by a dll's source file do not get triggered (set by symbol name works)
Breakpoints in the calling application set by source file and line are triggered.
>How-To-Repeat:
Create a dll and an application which uses the dll and build both with debugging symbols.

Start a debugging session and set a breakpoint on a dll-defined symbol by its name - it will be triggered.

Start a debugging session and set a breakpoint on a dll-function by its source file and line numbers - the program won't stop there.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: