Re: Xcode + gdb problems with exec
Re: Xcode + gdb problems with exec
- Subject: Re: Xcode + gdb problems with exec
- From: Etienne Samson <email@hidden>
- Date: Tue, 2 Sep 2008 13:52:42 +0200
Le 28 août 08 à 23:28, Thomas Engelmeier a écrit :
Hi,
I'm debugging an daemon that invokes "/sbin/ipfw" etc. with Xcode 3.1
As soon as my code invokes execl, I get the message
"Debugger error: Cannot access memory at address 0x4"
Is there anything I can do to prevent this?
TIA,
Tom_E
Hi !
I've been plagued by this for some time, and I still haven't found what's actually happening. Anyway, I have a workaround for this: it seems I can more consistently get under the debugger when I re-run directly under gdb (eg. entering "run" on the gdb prompt to bypass Xcode's Debug command).
If you want to reproduce it, try building the Quicksilver branch from source ;-). I have seen it happen even on some vanilla projects of mine too, which is quite inconvenient, but it really happens *every first time* when I try to debug QS.
Here's the run log of one of these failed runs :
[Session started at 2008-09-02 13:10:55 +0200.]
Loading program into debugger…
GNU gdb 6.3.50-20050815 (Apple version gdb-960) (Sun May 18 18:38:33 UTC 2008)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-apple-darwin".tty /dev/ttys002
Program loaded.
sharedlibrary apply-load-rules all
run
[Switching to process 4512 local thread 0x2d03]
bash(4512) malloc: recording malloc stacks to disk using standard recorder
bash(4512) malloc: process 4472 no longer exists, stack logs deleted from /tmp/stack-logs.4472.Quicksilver.LrrX89
bash(4512) malloc: stack logs being written into /tmp/stack-logs.4512.bash.hEiuof
arch(4512) malloc: recording malloc stacks to disk using standard recorder
arch(4512) malloc: stack logs deleted from /tmp/stack-logs.4512.bash.hEiuof
arch(4512) malloc: stack logs being written into /tmp/stack-logs.4512.arch.vLuhuK
Running…
Quicksilver(4512) malloc: recording malloc stacks to disk using standard recorder
Quicksilver(4512) malloc: stack logs deleted from /tmp/stack-logs.4512.arch.vLuhuK
Quicksilver(4512) malloc: stack logs being written into /tmp/stack-logs.4512.Quicksilver.PPVUb4
Quicksilver(4512) malloc: recording malloc stacks to disk using standard recorder
[Switching to process 4512 thread 0x5b03]
[Switching to process 4512 thread 0x5b03]
Program received signal: “EXC_BAD_ACCESS”.
Cannot access memory at address 0x4
Cannot access memory at address 0x4
(gdb) bt
#0 0xdeadbeef in ?? ()
Cannot access memory at address 0x4
(gdb)
Etienne |
_______________________________________________
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