Re: gdb problem
Re: gdb problem
- Subject: Re: gdb problem
- From: Jim Ingham <email@hidden>
- Date: Thu, 25 May 2006 09:31:27 -0700
BTW, if you file a bug on this and attach a little program that shows
this problemthat would be fantastic. Attaching the built binary as
well would be even better, since it would save me having to get and
install the pascal compiler. This same problem does show up
occasionally in optimized C & C++ as well, and we are working on it.
If we have some examples of the Pascal problem, we can try to get our
solution to work for that as well.
Thanks,
Jim
On May 25, 2006, at 9:22 AM, Jim Ingham wrote:
The algorithms for figuring out whether you have stepped into
another function or out of the current function when we step out of
the address range of the source line you were stepping in were
indeed changed in gdb-477. Actually, we didn't do this, this was a
change from the FSF gdb, not that that matters much... They were
made more strongly dependent on our being able to figure out what
happens in the function prologue of the function that we've just
stepped into. I wouldn't be all that surprised if the Free Pascal
Compiler generates prologue patterns that gdb doesn't fully
understand.
The sources to the gdb in Xcode 2.3 will show up shortly on:
http://www.opensource.apple.com/darwinsource/
It usually takes a week or so after the release for the tarball of
the sources to get posted.
Jim
On May 25, 2006, at 7:30 AM, Jonas Maebe wrote:
Hello,
The gdb from XCode 2.3 can no longer step over any function calls
in programs compiled with the Free Pascal Compiler (it generates
stabs debug information). The gdb "next" command always results in
stepping into the called function (i.e., the result is the same as
if you'd say "step"). This problem does not occur with previous
gdb's on Mac OS X, with gdb's on other platforms, or with gcc-
compiled code and the current gdb on Mac OS X.
I've been comparing the stabs we generate with those from gcc,
manually edited some stabs in both gcc-generated code and in our
generated code, but have not been able to change the behaviour of
either (i.e., "break" the gcc stabs or "fix" ours).
Can anyone tell me what changed between gdb-437 and gdb-477 in
this respect? And if not, where I can download the source for
gdb-477?
Jonas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden