following execve()

following execve()

[Justin Ferguson]

Hi,

What is the suggested method for following an execve() in an
application? I seem to remember I used to get a sigtrap, but not so
much anymore-- googling around I see that it looks like using tcatch
exec/cont/tbreak main is supposed to work, naturally it does not, the
break in main attempts to break in the original applications context,
and then it fails to be able to really do much of anything
(presumably) due to not properly attaching to the new process and not
being able to access it's memory. Then stack corruption occurs in the
target application, which causes gdb to just hang and requires me to
kill -9 it.

So how exactly am I supposed to do this?

Re: following execve()

[Daniel Jacobowitz]

On Tue, Jul 01, 2008 at 04:40:54AM +0000, Justin Ferguson wrote:
> Hi,
> 
> What is the suggested method for following an execve() in an
> application?

On what platform, with what version of GDB?

It should happen automatically with current versions of GDB on
GNU/Linux.  I believe HP/UX also.

-- 
Daniel Jacobowitz
CodeSourcery

Re: following execve()

[Justin Ferguson]

Hi,

gdb 6.7.1 on x86_64 linux, it works fine so long as I dont try to
break anywhere in the new process. The hang is something to do with
signals as a sigsegv should be getting delivered thats not, I'm not
incredibly concerned about that, but I'd sure like to be able to break
in the new process.

On Tue, Jul 1, 2008 at 5:42 AM, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Jul 01, 2008 at 04:40:54AM +0000, Justin Ferguson wrote:
>> Hi,
>>
>> What is the suggested method for following an execve() in an
>> application?
>
> On what platform, with what version of GDB?
>
> It should happen automatically with current versions of GDB on
> GNU/Linux.  I believe HP/UX also.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>

Re: following execve()

[Daniel Jacobowitz]

On Tue, Jul 01, 2008 at 03:16:31PM -0700, Justin Ferguson wrote:
> Hi,
> 
> gdb 6.7.1 on x86_64 linux, it works fine so long as I dont try to
> break anywhere in the new process. The hang is something to do with
> signals as a sigsegv should be getting delivered thats not, I'm not
> incredibly concerned about that, but I'd sure like to be able to break
> in the new process.

Try a current snapshot instead of 6.7.1 and see if that's better.

-- 
Daniel Jacobowitz
CodeSourcery

Re: following execve()

[Justin Ferguson]

Thanks, that appears to have fixed it.

On Tue, Jul 1, 2008 at 11:36 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Jul 01, 2008 at 03:16:31PM -0700, Justin Ferguson wrote:
>> Hi,
>>
>> gdb 6.7.1 on x86_64 linux, it works fine so long as I dont try to
>> break anywhere in the new process. The hang is something to do with
>> signals as a sigsegv should be getting delivered thats not, I'm not
>> incredibly concerned about that, but I'd sure like to be able to break
>> in the new process.
>
> Try a current snapshot instead of 6.7.1 and see if that's better.
>
> --
> Daniel Jacobowitz
> CodeSourcery
>