From: "Oldham, Adam" <adam.oldham@marconi.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Cc: "Oldham, Adam" <adam.oldham@marconi.com>
Subject: GDB 5, pascal, seeg faulting, questions....
Date: Thu, 31 May 2001 10:28:00 -0000 [thread overview]
Message-ID: <A3E34B558F5CD211B4980008C7A4A99003883A33@sparrow.eng.gilbarco.com> (raw)
I have a LARGE code base writtin in Pascal (GPC), Assembly(NASM) And C(GCC).
Its currently being ported to linux as for both development and runtime
environments. When running the native executable created, the code base
runs fine. However, when running gdb on the executable, I get a ton of seg
faults with my code before it reaches the point I want to break on. So, one
of my questions is, when you break on a thread other than the parent thread,
do all the threads stop execution or do they continue execution even though
one thread is stopped?
Now, my next question is in regards to Pascal in GDB only. I am using GDB
development version 20010529 (which has all the string errors from last week
fixed). In pascal you can have pointers just like in C. I have tested this
on C code. When you have a pointer in C it'll either print the value of
what you are pointing to or print the contents of the structure being
pointed to with no problem. In a Pascal Code Base, when printing the
contents of a variable on the GDB command line I get, "Attempt to
dereference a generic pointer", when doing something like this: "(gdb) p
Somepointer^". Doing "(gdb) p Somepointer" does return the memory address
sucessfully though.
Also, are there any plans to allow pascal in gdb to not be case sensitive?
Also, If I modify some things, would there be enough interest that I should
submit the changes?
Thanks,
ADam
-----------------------------------------------------------------------
C. Adam Oldham Marconi Commerce Systems Inc.
Software Engineer 7300 West Friendly Ave.
adam.oldham@marconi.com Greensboro, NC 27420-2087
Phone : 336.547.5952 Fax : 336.547.5079
-----------------------------------------------------------------------
This document contains confidential information of Marconi Commerce
Systems Inc. In consideration of the receipt of this document, the
recipient agrees not to reproduce, copy, use or transmit this document
and/or the information contained herein, in whole or in part, or to
suffer such actions by others, for any purpose except with written
permission, first obtained, of Marconi Commerce Systems Inc., and
further agrees to surrender the same to Marconi Commerce Systems Inc.
upon demand.
-----------------------------------------------------------------------
next reply other threads:[~2001-05-31 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 10:28 Oldham, Adam [this message]
2001-05-31 10:38 ` Daniel Berlin
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=A3E34B558F5CD211B4980008C7A4A99003883A33@sparrow.eng.gilbarco.com \
--to=adam.oldham@marconi.com \
--cc=gdb@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