bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem with line n.o's


From: Ramaswamy
Subject: Problem with line n.o's
Date: Fri, 19 Sep 2003 16:29:00 +0530

Hi,
    I am not sure if this is a bug or a missing feature. Here are the details -
 
Version of GDB : GNU gdb 5.3
 
Type of Machine: Red-hat Linux 6.0 on i686
 
What Compiler was used to compiler GDB: egcs-2.91.66
 
What compiler (and its version) was used to compile the program you are debugging: egcs-2.91.66
 
Source code for reproducing the behaviour: Any C File with well over 64K lines of code.
 
The behaviour - If a break point is set for a function which lies beyond the 64K line limit then even though it seemed to execute the program correctly it shows from the file the line <lineno> % 65536. I guess gdb aint displaying the correct line of the file being executed in those cases. If the control comes back to code with the 64K line limit then this problem does not exist. The line no displayed is consistent with <actuallineno> % 64K.
 
Yours Sincerely
Ramaswamy

"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." - Albert Einstein

Information contained and transmitted by this E-MAIL is proprietary to
Synergy Infotech Private Limited and is intended for use only by the
individual or entity to which it is addressed, and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law. If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a  person responsible for
delivering the information to the named recipient,  you are notified that any
use, distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. We have taken
precautions to minimize the risk of transmitting software viruses, but we
advise you to carry out your own virus checks on any attachment to this
message. We cannot accept liability for any loss or damage caused by software
viruses. If you have received this communication in error, please delete this
mail & notify us immediately at mailto:address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]