From: Chris Hamilton <chamilto@navtechinc.com>
To: Bruce Korb <bkorb@veritas.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, Bruce Korb <bkorb@gnu.org>,
gdb@sources.redhat.com
Subject: Re: popen
Date: Wed, 22 Jan 2003 14:23:00 -0000 [thread overview]
Message-ID: <3E2EA950.8020008@navtechinc.com> (raw)
In-Reply-To: <3E2D6310.3030307@navtechinc.com>
I didn't really think that odbc was causing the problem, so I linked in
another threaded library and got the same result. I think the general
case is that gdb loses it's brains anytime a threaded library is linked
in, a breakpoint is set and a popen is passed over. I've tried this
with a few safe libraries ( ie. libraries I didn't write ;) ), and this
seems to hold up.
Chris Hamilton wrote:
> The problem seems to come when I include the odbc libraries included
> with redhat 7.3. I've included a test .c file that will cause the
> problem when run with:
> cc popen_test.c -o a.out -g -lodbc
>
>
> Bruce Korb wrote:
>
>> Daniel Jacobowitz wrote:
>>
>>
>>> On Mon, Jan 20, 2003 at 01:30:04PM -0800, Bruce Korb wrote:
>>>
>>>
>>>> Chris Hamilton wrote:
>>>>
>>>>
>>>>> Bruce,
>>>>> I came across your September 24th posting about gdb throwing off a
>>>>> "Cannot find thread 2049" when it hits a popen
>>>>> (http://sources.redhat.com/ml/insight/2002-q3/msg00185.html).
>>>>> I'm currently experiencing the same problem in my application, and
>>>>> I was
>>>>> wondering if you had any advice on how to solve it.
>>>>>
>>>>
>>
>>
>>
>>> Popen should not present this problem. I don't know why it does, so we
>>> need more information.
>>>
>>
>>
>> It seems to occur when using popen, but not when I do all
>> the fork/exec stuff myself. I'll see if a trivial popen
>> example duplicates the problem, but I would guess that many
>> would have complained by now if it were that easy.
>>
>>
>>
>>> Meanwhile multi-process debugging is forthcoming. The Linux kernel
>>> patches are already in and I have more GDB patches queued.
>>>
>>
>>
>> Excellent!! Thank you very much!
>>
>>
>>
>------------------------------------------------------------------------
>
>#include <stdio.h>
>
>int main()
>{
>
>FILE *tpPipeFp;
>
>if((tpPipeFp = popen("test", "w")) == NULL)
> {
> printf("Can't open pipe\n");
> exit();
> }
>else
> printf("I've opened the pipe\n");
>
>pclose(tpPipeFp);
>
>}
>
>
>
prev parent reply other threads:[~2003-01-22 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E2C6377.5030600@navtechinc.com>
2003-01-20 21:30 ` popen Bruce Korb
2003-01-21 2:01 ` popen Daniel Jacobowitz
2003-01-21 3:16 ` popen Bruce Korb
2003-01-21 15:11 ` popen Chris Hamilton
2003-01-22 14:23 ` Chris Hamilton [this message]
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=3E2EA950.8020008@navtechinc.com \
--to=chamilto@navtechinc.com \
--cc=bkorb@gnu.org \
--cc=bkorb@veritas.com \
--cc=drow@mvista.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