Re: clean makehdimage

On 2005-09-07 at 02:55:03 [+0200], Stephan Aßmus <superstippi@...> wrote:
[...]

Please ignore this message, my girlfriend accidentally used the wrong mail 
daemon to "check" mail...

Best regards and happy new year to everyone!
-Stephan

user land debugger

Hi,

is GDB still supposed to come up in a Terminal when some app crashes? It 
doesn't happen here anymore, I just see a thread "debug task" in the team 
that has crashed.

Best regards,
-Stephan

Re: user land debugger

On 2006-01-02 at 14:50:23 [+0100], Stephan Assmus <superstippi@...> 
wrote:
> 
> is GDB still supposed to come up in a Terminal when some app crashes?

In a MiniTerminal, unless someone has changed that.

> It
> doesn't happen here anymore, I just see a thread "debug task" in the team
> that has crashed.

Doesn't sound good. I haven't changed anything at least.

CU, Ingo

Re: user land debugger

On 2006-01-02 at 16:02:29 [+0100], Ingo Weinhold
<bonefish@...> 
wrote:
> On 2006-01-02 at 14:50:23 [+0100], Stephan Assmus <superstippi@...>
> wrote:
> > 
> > is GDB still supposed to come up in a Terminal when some app crashes?
> 
> In a MiniTerminal, unless someone has changed that.
> 
> > It
> > doesn't happen here anymore, I just see a thread "debug task" in the team
> > that has crashed.
> 
> Doesn't sound good. I haven't changed anything at least.

I have examined the problem. The debug_server blocks on BAlert::Go() for the 
alert it wants to show (DebugServer.cpp:579). This would be just fine, if 
the alert would indeed appear on screen, which it doesn't. So, app server 
folks, it's your turn. 

If you need a reliably crashing app, add the following to your 
UserBuildConfig:

	AddFilesToHaikuImage beos bin : crashing_app ;

crashing_app can be invoked on the command line. It even has some fancy 
options to specify the kind of crash. The default is a boring SEGFAULT. 

Re: user land debugger

On 2006-01-02 at 22:20:40 [+0100], Ingo Weinhold
<bonefish@...> 
wrote:
> 
> On 2006-01-02 at 16:02:29 [+0100], Ingo Weinhold <bonefish@...>
> wrote:
> > On 2006-01-02 at 14:50:23 [+0100], Stephan Assmus <superstippi@...>
> > wrote:
> > > 
> > > is GDB still supposed to come up in a Terminal when some app crashes?
> > 
> > In a MiniTerminal, unless someone has changed that.
> > 
> > > It
> > > doesn't happen here anymore, I just see a thread "debug task" in the 
> > > team
> > > that has crashed.
> > 
> > Doesn't sound good. I haven't changed anything at least.
> 
> I have examined the problem. The debug_server blocks on BAlert::Go() for the
> alert it wants to show (DebugServer.cpp:579). This would be just fine, if
> the alert would indeed appear on screen, which it doesn't. So, app server
> folks, it's your turn. 

Axel, this might have something to do with modal windows that don't have 
"parent" windows. I mean, something with the subset stuff in the window 
manager. Do you have a quick idea or should I continue to investigate?

gcc4 version of Haiku?

hello everyone,

just curious if anyone's built gcc4 version of Haiku.
if so, what's the preferred OS/distro to use?

=mmadia

Re: gcc4 version of Haiku?

"mmadia" <mattmadia@...> wrote:
> just curious if anyone's built gcc4 version of Haiku.
> if so, what's the preferred OS/distro to use?

I'm not sure if I understand your question, but since the Haiku 
buildtools now include a GCC 4, you shouldn't depend on the OS hosting 
the build; it should work everywhere.

Bye,
   Axel.

Re: gcc4 version of Haiku?

On 2006-01-07 at 15:38:24 [+0100], Axel Dörfler <axeld@...> 
wrote:
> "mmadia" <mattmadia@...> wrote:
> > just curious if anyone's built gcc4 version of Haiku.
> > if so, what's the preferred OS/distro to use?
> 
> I'm not sure if I understand your question, but since the Haiku
> buildtools now include a GCC 4, you shouldn't depend on the OS hosting
> the build; it should work everywhere.

Er, I've never tested whether gcc4 builds under BeOS. It may well be that I 
left out some patches necessary for BeOS. All I can say is that it runs 
fine under my SuSE Linux 9.2 installation (updated to gcc4 meanwhile). I 
suppose most other Linux distributions will work, too. Nathan checked 
something in for FreeBSD; not sure how far he got there. Axel reported 
problems under YellowDog Linux (PPC), so I wouldn't expect that one to work.

CU, Ingo

Re: gcc4 version of Haiku?

Ingo Weinhold wrote:

>On 2006-01-07 at 15:38:24 [+0100], Axel Dörfler <axeld@...> 
>wrote:
>  
>
>>"mmadia" <mattmadia@...> wrote:
>>    
>>
>>>just curious if anyone's built gcc4 version of Haiku.
>>>if so, what's the preferred OS/distro to use?
>>>      
>>>
>>I'm not sure if I understand your question, but since the Haiku
>>buildtools now include a GCC 4, you shouldn't depend on the OS hosting
>>the build; it should work everywhere.
>>    
>>
>
>Er, I've never tested whether gcc4 builds under BeOS. It may well be that I 
>left out some patches necessary for BeOS. All I can say is that it runs 
>fine under my SuSE Linux 9.2 installation (updated to gcc4 meanwhile). I 
>suppose most other Linux distributions will work, too. Nathan checked 
>something in for FreeBSD; not sure how far he got there. Axel reported 
>problems under YellowDog Linux (PPC), so I wouldn't expect that one to work
>  
>

I'm still having a bunch of issues on FreeBSD. The toolchain compiles 
and runs fine, but there are linker problems when I try to build Haiku 

Via C3 and Haiku boot