Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "josef ezra" <jezra@emc.com>
To: <gdb-patches@sources.redhat.com>
Subject: should gdb require '.text' and '.data' sections?
Date: Thu, 18 Apr 2002 08:11:00 -0000	[thread overview]
Message-ID: <02ea01c1e6eb$65f850c0$ad219fa8@lss.emc.com> (raw)

Hello

I'm trying to debug a symbol file that has no '.text' section. Unlike 5.0
version, the new SECT_OFF_TEXT(objfile) macro calls (no-return) internal
error and prevent the read.

Should gdb work that way (requiring '.text' and '.data' sections)?

If not, can we consider the first sections flagged 'SEC_CODE'/'SEC_DATA' as
substitutes? Or maybe better have a default 0/1 values (like 5.0)? Both
should work in my case.

- Jezra





             reply	other threads:[~2002-04-18 15:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  8:11 josef ezra [this message]
2002-04-18 11:15 ` Michael Snyder
2002-04-22  6:32   ` Josef Ezra
2002-04-24  6:45   ` [RFA] " Josef Ezra
2002-06-13 10:06   ` Request for new gdb command: 'info orientation' Josef Ezra
2002-06-13 10:35     ` Andrew Cagney
2002-06-13 11:06     ` Michael Snyder
2002-06-13 11:20       ` Josef Ezra
2002-06-17 12:34       ` [RFA] new command: 'maintenance info lines' Josef Ezra
2002-06-17 22:26         ` Eli Zaretskii
2002-06-18 13:47           ` josef ezra
2002-06-18 14:42             ` Michael Snyder
2002-06-18 22:42             ` Eli Zaretskii
2002-06-19  7:27               ` Josef Ezra
2002-06-18 14:35         ` Michael Snyder
2002-09-06  5:08           ` Josef Ezra
2002-09-18 22:33             ` Eli Zaretskii
2002-09-23  8:06               ` Josef Ezra
2002-09-23 22:12                 ` Eli Zaretskii
2002-09-25 13:26             ` Fernando Nasser
2002-09-26  6:49               ` Josef Ezra
2002-09-26 10:45                 ` Fernando Nasser
2002-09-26 19:03                   ` Andrew Cagney
2002-09-06 13:44           ` Josef Ezra

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='02ea01c1e6eb$65f850c0$ad219fa8@lss.emc.com' \
    --to=jezra@emc.com \
    --cc=gdb-patches@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